From: Andrew Morton <akpm@osdl.org>
To: Jesse Huang <jesse@icplus.com.tw>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org, jgarzik@pobox.com
Subject: Re: [PATCH] Restore the original TX FIFO overflow process.
Date: Fri, 22 Sep 2006 21:54:11 -0700 [thread overview]
Message-ID: <20060922215411.85ac3f16.akpm@osdl.org> (raw)
In-Reply-To: <1158953401.2630.0.camel@localhost.localdomain>
On Fri, 22 Sep 2006 15:30:01 -0400
Jesse Huang <jesse@icplus.com.tw> wrote:
> #define DRV_NAME "sundance"
> -#define DRV_VERSION "1.01+LK1.14"
> -#define DRV_RELDATE "04-Aug-2006"
> +#define DRV_VERSION "1.01+LK1.15"
> +#define DRV_RELDATE "22-Sep-2006"
Can we please delete this thing? It's *forever* getting rejects and
people only remember to update it a fraction of the time anyway.
next prev parent reply other threads:[~2006-09-23 4:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-22 19:30 [PATCH] Restore the original TX FIFO overflow process Jesse Huang
2006-09-23 4:54 ` Andrew Morton [this message]
2006-09-23 8:50 ` Andrew Morton
[not found] ` <20060923015157.b4014c6a.akpm@osdl.org>
2006-09-25 1:20 ` Jesse Huang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060922215411.85ac3f16.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=jesse@icplus.com.tw \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).