[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAMuHMdWYdKPgVR8hvcXN1qmm7nqCyjWV3NPHzdVHG_H8F20-3w@mail.gmail.com>
Date: Fri, 5 Oct 2012 07:05:43 +0200
From: Geert Uytterhoeven <geert@...ux-m68k.org>
To: David Howells <dhowells@...hat.com>
Cc: linux-m68k@...r.kernel.org, linux-kernel@...r.kernel.org,
Linux-Arch <linux-arch@...r.kernel.org>
Subject: Re: [GIT PULL] Disintegrate UAPI for m68k
On Thu, Oct 4, 2012 at 9:51 PM, David Howells <dhowells@...hat.com> wrote:
> git://git.infradead.org/users/dhowells/linux-headers.git disintegrate-m68k
>
> for you to fetch changes up to b039235da939b28c539b3e1b4566107a9bdbdef8:
>
> UAPI: (Scripted) Disintegrate arch/m68k/include/asm (2012-10-04 18:20:56 +0100)
>
> ----------------------------------------------------------------
> David Howells (6):
> UAPI: Fix the guards on various asm/unistd.h files
> UAPI: Split compound conditionals containing __KERNEL__ in Arm64
> Merge remote-tracking branch 'c6x/for-linux-next' into uapi-prep
> UAPI: Fix conditional header installation handling (notably kvm_para.h on m68k)
> UAPI: (Scripted) Disintegrate include/asm-generic
> UAPI: (Scripted) Disintegrate arch/m68k/include/asm
>
> Mark Salter (2):
> c6x: make dsk6455 the default config
> c6x: remove c6x signal.h
I assume these c6x and asm-generic changes are the ones you just asked Linus
to pull? Doesn't it make more sense to ask us (the individual arch maintainers)
to pull our parts after Linus has pulled the generic part?
Do you want this ("our parts") to go in 3.7 or 3.8?
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@...ux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists