All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Harvey Harrison <harvey.harrison@gmail.com>
Cc: torvalds@linux-foundation.org, linux-arch@vger.kernel.org
Subject: Re: [PATCH-mm] byteorder: wire up arches to use new headers
Date: Thu, 17 Jul 2008 16:44:51 -0700	[thread overview]
Message-ID: <20080717164451.99377cdb.akpm@linux-foundation.org> (raw)
In-Reply-To: <1216337353.6029.66.camel@brick>

On Thu, 17 Jul 2008 16:29:13 -0700
Harvey Harrison <harvey.harrison@gmail.com> wrote:

> Acked-by: Haavard Skinnemoen <haavard.skinnemoen@atmel.com>
> Signed-off-by: Harvey Harrison <harvey.harrison@gmail.com>
> ---
> AKPM, this is the arch wire-up, has ack for AVR32, if you want
> one-per-arch, just ask, but this at least gets it out there.

Well there are two approaches

a) one-per-arch.  We merge the base patches and once they're in
   mainline I trickle the per-arch patches out to maintainers.

b) single megapatch.  I gather as many acks as poss them slam it all
   into 2.6.28-rc1.


Option a) is more work and fuss for everyone, but it does produce a
better end result.  People look more closely at the change and it gets
better testing, etc.

Once I get my mm-into-linux-next act together things will be better -
at least the megapatch would be in linux-next and as the
arch maintainers are testing linux-next (rofl) any problems _should_ be
detected.

So, err, umm, looking at the fiddliness of this stuff, yes, I think
one-per-arch would be a little bit better, please.

  reply	other threads:[~2008-07-17 23:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-17 23:29 [PATCH-mm] byteorder: wire up arches to use new headers Harvey Harrison
2008-07-17 23:44 ` Andrew Morton [this message]
2008-07-18 13:36 ` Russell King

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=20080717164451.99377cdb.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=harvey.harrison@gmail.com \
    --cc=linux-arch@vger.kernel.org \
    --cc=torvalds@linux-foundation.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.