From: Christoph Hellwig <hch@lst.de>
To: David Miller <davem@davemloft.net>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH 2/3] add dev_to_node()
Date: Tue, 7 Nov 2006 00:39:00 +0100 [thread overview]
Message-ID: <20061106233900.GA7148@lst.de> (raw)
In-Reply-To: <20061105.002237.18309940.davem@davemloft.net>
On Sun, Nov 05, 2006 at 12:22:37AM -0800, David Miller wrote:
> Looks good to me.
So what's the right path to get this in? There's one patch touching
MM code, one adding something to the driver core and then finally a
networking patch depending on the previous two. Do you want to take
them all and send them in through the networking tree? Or should
we put the burden on Andrew?
next prev parent reply other threads:[~2006-11-06 23:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20061030141501.GC7164@lst.de>
[not found] ` <20061030.143357.130208425.davem@davemloft.net>
[not found] ` <20061104225629.GA31437@lst.de>
[not found] ` <20061104230648.GB640@redhat.com>
2006-11-04 23:09 ` [PATCH 2/3] add dev_to_node() Christoph Hellwig
2006-11-04 23:53 ` Christoph Hellwig
2006-11-05 8:22 ` David Miller
2006-11-06 23:39 ` Christoph Hellwig [this message]
2006-11-07 6:25 ` Ravikiran G Thirumalai
2006-11-07 10:15 ` Christoph Hellwig
2006-10-30 14:15 Christoph Hellwig
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=20061106233900.GA7148@lst.de \
--to=hch@lst.de \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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).