From: "Yinghai Lu" <yhlu.kernel@gmail.com>
To: "Stefan Richter" <stefanr@s5r6.in-berlin.de>
Cc: "Andrew Morton" <akpm@linux-foundation.org>,
ak@suse.de, clameter@sgi.com, cornelia.huck@de.ibm.com,
davem@davemloft.net, greg@kroah.com, hch@infradead.org,
rientjes@google.com,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 3/10] try parent numa_node at first before using default v2
Date: Tue, 24 Jul 2007 10:32:37 -0700 [thread overview]
Message-ID: <86802c440707241032u21fc6150gb1cf52678e97b1ab@mail.gmail.com> (raw)
In-Reply-To: <46A5C105.20707@s5r6.in-berlin.de>
On 7/24/07, Stefan Richter <stefanr@s5r6.in-berlin.de> wrote:
> On 7/23/2007 10:23 PM, Yinghai Lu wrote:
> > this one already in -mm, but it needs [PATCH 1/10]
> >
> > [PATCH 3/10] try parent numa_node at first before using default v2
> [...]
> > this patch is using second method.
> [...]
>
> Could you shorten the patch description?
>
> Don't describe what your patch _does not_ do. Don't even describe _how_
> your patch does what it does (unless it's obfuscated, but then that
> would be a bad patch anyway).
>
> Just describe _why_ it does something.
> --
Please check it is OK.
[PATCH 3/10] try parent numa_node at first before using default v2
in the device_add, we try to use use parent numa_node.
need to make sure pci root bus's bridge device numa_node is set.
then we could use device->numa_node direclty for all device.
and don't need to call pcibus_to_node().
Signed-off-by: Yinghai Lu <yinghai.lu@sun.com>
prev parent reply other threads:[~2007-07-24 17:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-23 20:23 Yinghai Lu
2007-07-24 9:06 ` Stefan Richter
2007-07-24 17:32 ` Yinghai Lu [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=86802c440707241032u21fc6150gb1cf52678e97b1ab@mail.gmail.com \
--to=yhlu.kernel@gmail.com \
--cc=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=clameter@sgi.com \
--cc=cornelia.huck@de.ibm.com \
--cc=davem@davemloft.net \
--cc=greg@kroah.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rientjes@google.com \
--cc=stefanr@s5r6.in-berlin.de \
/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
all inboxes | Powered by JetHome®