From: "Guo-Fu Tseng" <cooldavid@cooldavid.org>
To: "David Miller" <davem@davemloft.net>
Cc: "netdev" <netdev@vger.kernel.org>,
"Ethan Hsiao" <ethanhsiao@jmicron.com>
Subject: [PATCH net-2.6 0/7] jme: Jme driver bug fix patches
Date: Mon, 6 Jul 2009 23:04:37 +0800 [thread overview]
Message-ID: <20090706150151.M5056@cooldavid.org> (raw)
In-Reply-To: <20090706145548.9CCA5122E3@cooldavid.org>
Dear David:
I've resend the patchset against latest net-next-2.6, thank you for your help.
Signed-off-by: Guo-Fu Tseng <cooldavid@cooldavid.org>
next prev parent reply other threads:[~2009-07-06 15:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-06 14:36 [PATCH net-2.6 1/7] jme: Some minor coding style consistency modifications Guo-Fu Tseng
2009-07-06 15:04 ` Guo-Fu Tseng [this message]
2009-07-06 19:24 ` [PATCH net-2.6 0/7] jme: Jme driver bug fix patches David Miller
2009-07-06 20:06 ` David Miller
2009-07-06 19:23 ` [PATCH net-2.6 1/7] jme: Some minor coding style consistency modifications David Miller
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=20090706150151.M5056@cooldavid.org \
--to=cooldavid@cooldavid.org \
--cc=davem@davemloft.net \
--cc=ethanhsiao@jmicron.com \
--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).