From: David Miller <davem@davemloft.net>
To: Jie.Yang@Atheros.com
Cc: joe@perches.com, netdev@vger.kernel.org, yanghy@cn.fujitsu.com,
akpm@linux-foundation.org
Subject: Re: [PATCH] atl1c_main.c: add wait_for_idle routine
Date: Mon, 01 Jun 2009 03:14:14 -0700 (PDT) [thread overview]
Message-ID: <20090601.031414.240581040.davem@davemloft.net> (raw)
In-Reply-To: <72981EBCFD196144B7C6999B9FC34A9A418BFD1261@SHEXMB-01.global.atheros.com>
From: Jie Yang <Jie.Yang@Atheros.com>
Date: Mon, 1 Jun 2009 14:59:17 +0800
> On Monday, June 01, 2009 2:45 PM
> Joe Perches <joe@perches.com> wrote:
>> Slight refactoring of duplicated wait for idle checks Spelling fix
>>
>> Signed-off-by: Joe Perches <joe@perches.com>
...
> Acked-by: jie.yang@atheros.com
Applied to net-next-2.6, thanks.
prev parent reply other threads:[~2009-06-01 10:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-01 6:44 [PATCH] atl1c_main.c: add wait_for_idle routine Joe Perches
2009-06-01 6:59 ` Jie Yang
2009-06-01 10:14 ` David Miller [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=20090601.031414.240581040.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=Jie.Yang@Atheros.com \
--cc=akpm@linux-foundation.org \
--cc=joe@perches.com \
--cc=netdev@vger.kernel.org \
--cc=yanghy@cn.fujitsu.com \
/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).