From: Bryan Wu <bryan.wu@analog.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
netdev@vger.kernel.org, torvalds@linux-foundation.org,
akpm@linux-foundation.org
Subject: Re: [patch 089/181] Blackfin: on-chip ethernet MAC controller driver
Date: Wed, 23 May 2007 17:16:11 +0800 [thread overview]
Message-ID: <1179911772.10328.19.camel@roc-desktop> (raw)
In-Reply-To: <465405A1.5030409@garzik.org>
On Wed, 2007-05-23 at 05:13 -0400, Jeff Garzik wrote:
> Bryan Wu wrote:
> > Hi Jeff:
> >
> > Could you please review this patch? Sorry for miss sending the patch to
> > you for review at beginning.
>
> can you resend as a patch rather than a quoted patch?
>
> Jeff
>
>
Oh, sorry, I forgot this. It will be sent ASAP.
Thanks Jeff,
-Bryan
prev parent reply other threads:[~2007-05-23 9:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200705062150.l46LoVWQ024648@shell0.pdx.osdl.net>
2007-05-07 0:20 ` [patch 089/181] Blackfin: on-chip ethernet MAC controller driver Jeff Garzik
2007-05-07 3:40 ` Randy Dunlap
[not found] ` <1179909013.10328.9.camel@roc-desktop>
[not found] ` <465405A1.5030409@garzik.org>
2007-05-23 9:16 ` Bryan Wu [this message]
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=1179911772.10328.19.camel@roc-desktop \
--to=bryan.wu@analog.com \
--cc=akpm@linux-foundation.org \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=torvalds@linux-foundation.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).