From: Jeff Garzik <jgarzik@pobox.com>
To: Andrew Morton <akpm@osdl.org>
Cc: Hirokazu Takata <takata.hirokazu@renesas.com>,
takata@linux-m32r.org, linux-kernel@vger.kernel.org,
paul.mundt@nokia.com, nico@cam.org, netdev@oss.sgi.com
Subject: Re: [PATCH 2.6.9-rc4-mm1] [m32r] Fix smc91x driver for m32r
Date: Thu, 14 Oct 2004 10:21:51 -0400 [thread overview]
Message-ID: <416E8B7F.9050401@pobox.com> (raw)
In-Reply-To: <20041012223227.45a62301.akpm@osdl.org>
> smc91x-revert-11923358-m32r-modify-drivers-net-smc91xc.patch
> smc91x-assorted-minor-cleanups.patch
> smc91x-set-the-mac-addr-from-the-smc_enable-function.patch
> smc91x-fold-smc_setmulticast-into-smc_set_multicast_list.patch
> smc91x-simplify-register-bank-usage.patch
> smc91x-move-tx-processing-out-of-irq-context-entirely.patch
> smc91x-use-a-work-queue-to-reconfigure-the-phy-from.patch
> smc91x-fix-possible-leak-of-the-skb-waiting-for-mem.patch
> smc91x-display-pertinent-register-values-from-the.patch
> smc91x-straighten-smp-locking.patch
> smc91x-cosmetics.patch
> m32r-trivial-fix-of-smc91xh.patch
> smc91x-fix-smp-lock-usage.patch
> smc91x-more-smp-locking-fixes.patch
> smc91x-fix-compilation-with-dma-on-pxa2xx.patch
> smc91x-receives-two-bytes-too-many.patch
> smc91x-release-on-chip-rx-packet-memory-asap.patch
>
> I'll unload all those onto Jeff...
I'll wait for these patches, and drop other smc91x patches...
Jeff
prev parent reply other threads:[~2004-10-14 14:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20041012.195043.137811384.takata.hirokazu@renesas.com>
[not found] ` <416BFD79.1010306@pobox.com>
2004-10-13 1:52 ` [PATCH 2.6.9-rc4-mm1] [m32r] Fix smc91x driver for m32r Hirokazu Takata
2004-10-13 2:08 ` Jeff Garzik
2004-10-13 3:15 ` Hirokazu Takata
2004-10-13 5:32 ` Andrew Morton
2004-10-14 10:30 ` Russell King
2004-10-14 13:46 ` Nicolas Pitre
2004-10-14 14:21 ` 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=416E8B7F.9050401@pobox.com \
--to=jgarzik@pobox.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=nico@cam.org \
--cc=paul.mundt@nokia.com \
--cc=takata.hirokazu@renesas.com \
--cc=takata@linux-m32r.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).