From: Paul Mackerras <paulus@samba.org>
To: David Miller <davem@davemloft.net>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: Patches added to powerpc.git powerpc-next and master branches
Date: Mon, 7 Apr 2008 22:25:15 +1000 [thread overview]
Message-ID: <18426.4779.937007.883268@cargo.ozlabs.ibm.com> (raw)
In-Reply-To: <20080406.232220.69225114.davem@davemloft.net>
David Miller writes:
> Please let me know if you're going to require that I fix a bug that
> already exists in the LMB code just to get my NUMA node LMB allocation
> support patch in.
My thought was to put your patch in as-is with another patch to fix
the existing bug either immediately before it or immediately after
it. I started reading through lmb.c again today but got distracted by
some other things. It looks like lmb.c could use a bit of a coding
style cleanup, if nothing else.
> Please be straightforward and don't just drop the patch quietly in
> situations like this, let me know what you want to happen in order to
> add the change.
I haven't dropped it, it's just that I haven't got through all of the
patches for .26 yet.
Paul.
next prev parent reply other threads:[~2008-04-07 12:25 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-07 5:52 Patches added to powerpc.git powerpc-next and master branches Paul Mackerras
2008-04-07 6:22 ` David Miller
2008-04-07 12:25 ` Paul Mackerras [this message]
2008-04-10 11:07 ` Ishizaki Kou
2008-04-15 11:08 ` Paul Mackerras
2008-04-15 21:48 ` Benjamin Herrenschmidt
-- strict thread matches above, loose matches on Subject: below --
2008-04-10 11:46 Laurent Pinchart
2008-04-10 12:32 ` Paul Mackerras
2008-04-10 14:11 ` Kumar Gala
2008-04-10 14:28 ` Laurent Pinchart
2008-04-10 14:33 ` Kumar Gala
2008-04-10 14:10 ` Kumar Gala
2008-04-10 14:20 ` Laurent Pinchart
2008-04-10 14:44 ` Kumar Gala
2008-03-25 22:35 Paul Mackerras
2008-03-26 0:54 ` Josh Boyer
2008-03-26 6:00 ` Grant Likely
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=18426.4779.937007.883268@cargo.ozlabs.ibm.com \
--to=paulus@samba.org \
--cc=davem@davemloft.net \
--cc=linuxppc-dev@ozlabs.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).