From: Jeff Garzik <jeff@garzik.org>
To: akpm@linux-foundation.org
Cc: netdev@vger.kernel.org, cooloney@kernel.org, dsaxena@plexity.net,
lethal@linux-sh.org, nico@cam.org, rmk+kernel@arm.linux.org.uk
Subject: Re: [patch for 2.6.25? 1/3] smc91x: fix build breakage from the SMC_GET_MAC_ADDR API upgrade
Date: Thu, 27 Mar 2008 08:22:56 -0400 [thread overview]
Message-ID: <47EB91A0.8040902@garzik.org> (raw)
In-Reply-To: <200803270745.m2R7jAX2024160@imap1.linux-foundation.org>
akpm@linux-foundation.org wrote:
> From: Bryan Wu <cooloney@kernel.org>
>
> Cc: Jeff Garzik <jeff@garzik.org>
> Cc: Deepak Saxena <dsaxena@plexity.net>
> Cc: Nicolas Pitre <nico@cam.org>
> Cc: Russell King <rmk+kernel@arm.linux.org.uk>
> Cc: Paul Mundt <lethal@linux-sh.org>
> Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
> ---
>
> drivers/net/smc91x.h | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
davem already has this
prev parent reply other threads:[~2008-03-27 12:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-27 7:45 [patch for 2.6.25? 1/3] smc91x: fix build breakage from the SMC_GET_MAC_ADDR API upgrade akpm
2008-03-27 12:22 ` Jeff Garzik [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=47EB91A0.8040902@garzik.org \
--to=jeff@garzik.org \
--cc=akpm@linux-foundation.org \
--cc=cooloney@kernel.org \
--cc=dsaxena@plexity.net \
--cc=lethal@linux-sh.org \
--cc=netdev@vger.kernel.org \
--cc=nico@cam.org \
--cc=rmk+kernel@arm.linux.org.uk \
/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).