From: catalin.marinas@arm.com (Catalin Marinas)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] Disintegrate UAPI for arm64
Date: Thu, 4 Oct 2012 21:22:05 +0100 [thread overview]
Message-ID: <20121004202204.GA6256@arm.com> (raw)
In-Reply-To: <17350.1349380264@warthog.procyon.org.uk>
On Thu, Oct 04, 2012 at 08:51:04PM +0100, David Howells wrote:
> Can you merge the following branch into the arm64 tree please.
>
> This is to complete part of the UAPI disintegration for which the preparatory
> patches were pulled recently.
>
> Note that there are some fixup patches which are at the base of the branch
> aimed at you, plus all arches get the asm-generic branch merged in too.
>
> The following changes since commit 612a9aab56a93533e76e3ad91642db7033e03b69:
>
> Merge branch 'drm-next' of git://people.freedesktop.org/~airlied/linux (2012-10-03 23:29:23 -0700)
>
> are available in the git repository at:
>
>
> git://git.infradead.org/users/dhowells/linux-headers.git disintegrate-arm64
>
> for you to fetch changes up to ae4f6c65798014d5d7a88d03e58faba53c0a92e1:
>
> UAPI: (Scripted) Disintegrate arch/arm64/include/asm (2012-10-04 18:20:24 +0100)
...
> arch/c6x/Makefile | 2 +
> arch/c6x/include/asm/Kbuild | 1 +
> arch/c6x/include/asm/signal.h | 17 -
> arch/c6x/include/asm/unistd.h | 4 -
> arch/hexagon/include/asm/unistd.h | 5 -
> arch/openrisc/include/asm/unistd.h | 5 -
> arch/score/include/asm/unistd.h | 5 -
> arch/tile/include/asm/unistd.h | 5 -
> arch/unicore32/include/asm/unistd.h | 4 -
It seems that this branch contains more than just arm64 changes. Are
they going into mainline separately?
--
Catalin
prev parent reply other threads:[~2012-10-04 20:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-04 19:51 [GIT PULL] Disintegrate UAPI for arm64 David Howells
2012-10-04 20:22 ` Catalin Marinas [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=20121004202204.GA6256@arm.com \
--to=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.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).