From: Jeff Garzik <jeff@garzik.org>
To: Ben Dooks <ben-linux@fluff.org>
Cc: Linux Networking <netdev@vger.kernel.org>, akpm@linux-foundation.org
Subject: Re: DM9000 patches
Date: Mon, 28 Apr 2008 11:21:00 -0400 [thread overview]
Message-ID: <4815EB5C.4020505@garzik.org> (raw)
In-Reply-To: <20080428151309.GA30439@fluff.org.uk>
Ben Dooks wrote:
> I would like to find out the state of the DM9000 patches
> which where submitted. Is it possible for these to be
> queued either into the network driver tree, or into -mm?
>
> The messages are:
>
> http://marc.info/?l=linux-netdev&m=120818415110509&w=2
this is in the queue
> http://marc.info/?l=linux-netdev&m=120851343125997&w=2
> http://marc.info/?l=linux-netdev&m=120851419927097&w=2
these two are not. It sounded like your comments may have impacted your
ack, and also, when there are multiple patches in the air from multiple
people, it's generally up to the maintainer to sort them all out and
send them in a batch.
Lastly, a CC to me would be quite helpful. I tend to scan subject lines
on netdev rather than read every message, and sometimes patches can get
missed.
Jeff
next prev parent reply other threads:[~2008-04-28 15:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-28 15:13 DM9000 patches Ben Dooks
2008-04-28 15:21 ` Jeff Garzik [this message]
2008-05-06 16:25 ` Jeff Garzik
2008-05-08 10:28 ` Ben Dooks
2008-05-08 10:33 ` DM9000: Add __devinit and __devexit attributes to probe and remove Ben Dooks
2008-05-13 5:18 ` Jeff Garzik
2008-05-08 10:35 ` DM9000: Update and fix driver debugging messages Ben Dooks
2008-05-08 10:36 ` DM9000: Use delayed work to update MII PHY state Ben Dooks
2008-05-08 20:11 ` Andrew Morton
2008-05-08 20:18 ` Andrew Morton
2008-05-12 20:27 ` Ben Dooks
-- strict thread matches above, loose matches on Subject: below --
2013-12-18 15:45 dm9000 patches Sascha Hauer
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=4815EB5C.4020505@garzik.org \
--to=jeff@garzik.org \
--cc=akpm@linux-foundation.org \
--cc=ben-linux@fluff.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.