From: Catalin Marinas <catalin.marinas@arm.com>
To: David Howells <dhowells@redhat.com>
Cc: "linux-arch@vger.kernel.org" <linux-arch@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/4] uapi: Allow automatic generation of trivial headers
Date: Thu, 11 Oct 2012 17:52:20 +0100 [thread overview]
Message-ID: <20121011165220.GD10659@arm.com> (raw)
In-Reply-To: <19626.1349974000@warthog.procyon.org.uk>
On Thu, Oct 11, 2012 at 05:46:40PM +0100, David Howells wrote:
> Catalin Marinas <catalin.marinas@arm.com> wrote:
>
> > The asm/Kbuild allows automatic generation of header files by specifying
> > "generic-y += ...". The first patch in the series allows the same thing
> > to be specified in uapi/asm/Kbuild.
> >
> > The subsequent patches remove some of the trivial header files in arm64,
> > s390 and sparc. Please note that the series has only been tested on
> > arm64. I can test the others but not until tomorrow.
>
> It should be noted that the arm64 patch is dependent on the disintegrate-arm64
> branch of my UAPI disintegration patches, which I don't believe is upstream
> yet.
Not yet. But this series is not meant for this merging window anyway.
--
Catalin
prev parent reply other threads:[~2012-10-11 16:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-11 16:18 [PATCH 0/4] uapi: Allow automatic generation of trivial headers Catalin Marinas
2012-10-11 16:18 ` [PATCH 1/4] uapi: Allow automatic generation of uapi/asm/ header files Catalin Marinas
2012-10-11 16:18 ` Catalin Marinas
2012-10-11 16:18 ` [PATCH 2/4] arm64: Automatically generate UAPI stat.h and unistd.h headers Catalin Marinas
2012-10-11 16:18 ` [PATCH 3/4] s390: Automatically generate trivial UAPI headers Catalin Marinas
2012-10-11 16:18 ` Catalin Marinas
2012-10-11 16:18 ` [PATCH 4/4] sparc: " Catalin Marinas
2012-10-11 19:13 ` David Miller
2012-10-11 16:46 ` [PATCH 0/4] uapi: Allow automatic generation of trivial headers David Howells
2012-10-11 16:52 ` 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=20121011165220.GD10659@arm.com \
--to=catalin.marinas@arm.com \
--cc=dhowells@redhat.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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).