From: Arjan van de Ven <arjan@infradead.org>
To: Jeff Garzik <jeff@garzik.org>
Cc: linux-ide@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH] ide/net: flip the order of SATA and network init
Date: Tue, 27 Jan 2009 16:48:42 -0800 [thread overview]
Message-ID: <20090127164842.0b73cc46@infradead.org> (raw)
In-Reply-To: <497F9A49.6060601@garzik.org>
On Tue, 27 Jan 2009 18:35:37 -0500
Jeff Garzik <jeff@garzik.org> wrote:
> ACK, ok with me too
>
ok so... which tree should this go via?
I would guess jgarzik's because he deals with both sata and net ;)
Jeff... how do you want to handle this?
--
Arjan van de Ven Intel Open Source Technology Centre
For development, discussion and tips for power savings,
visit http://www.lesswatts.org
next prev parent reply other threads:[~2009-01-28 0:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-27 22:19 [PATCH] ide/net: flip the order of SATA and network init Arjan van de Ven
2009-01-27 22:26 ` David Miller
2009-01-27 23:35 ` Jeff Garzik
2009-01-28 0:48 ` Arjan van de Ven [this message]
2009-01-28 1:23 ` David Miller
2009-01-28 1:59 ` Jeff Garzik
2009-01-28 0:22 ` Bartlomiej Zolnierkiewicz
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=20090127164842.0b73cc46@infradead.org \
--to=arjan@infradead.org \
--cc=jeff@garzik.org \
--cc=linux-ide@vger.kernel.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 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).