Re: [PATCH-mm] byteorder: wire up arches to use new headers

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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

> Acked-by: Haavard Skinnemoen <haavard.skinnemoen@xxxxxxxxx>
> Signed-off-by: Harvey Harrison <harvey.harrison@xxxxxxxxx>
> ---
> 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.
--
To unsubscribe from this list: send the line "unsubscribe linux-arch" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Kernel]     [Kernel Newbies]     [x86 Platform Driver]     [Netdev]     [Linux Wireless]     [Netfilter]     [Bugtraq]     [Linux Filesystems]     [Yosemite Discussion]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Device Mapper]

  Powered by Linux