linux-arch.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: James Hogan <james.hogan@imgtec.com>
To: Michal Marek <mmarek@suse.com>
Cc: Arnd Bergmann <arnd@arndb.de>,
	linux-kernel@vger.kernel.org,
	Heinrich Schuchardt <xypron.glpk@gmx.de>,
	Ralf Baechle <ralf@linux-mips.org>,
	Paul Burton <paul.burton@imgtec.com>,
	Florian Fainelli <f.fainelli@gmail.com>,
	linux-kbuild@vger.kernel.org, linux-arch@vger.kernel.org,
	linux-mips@linux-mips.org
Subject: Re: [PATCH v2 2/2] kbuild: Remove stale asm-generic wrappers
Date: Tue, 23 Feb 2016 09:51:07 +0000	[thread overview]
Message-ID: <20160223095107.GC21143@jhogan-linux.le.imgtec.org> (raw)
In-Reply-To: <4206493.gjdgtfndZ8@wuerfel>

[-- Attachment #1: Type: text/plain, Size: 2089 bytes --]

Hi Michal,

On Tue, Jan 19, 2016 at 03:27:24PM +0100, Arnd Bergmann wrote:
> On Tuesday 19 January 2016 14:22:13 James Hogan wrote:
> > On Tue, Jan 19, 2016 at 03:09:14PM +0100, Arnd Bergmann wrote:
> > > On Tuesday 19 January 2016 13:37:50 James Hogan wrote:
> > > > When a header file is removed from generic-y (often accompanied by the
> > > > addition of an arch specific header), the generated wrapper file will
> > > > persist, and in some cases may still take precedence over the new arch
> > > > header.
> > > > 
> > > > For example commit f1fe2d21f4e1 ("MIPS: Add definitions for extended
> > > > context") removed ucontext.h from generic-y in arch/mips/include/asm/,
> > > > and added an arch/mips/include/uapi/asm/ucontext.h. The continued use of
> > > > the wrapper when reusing a dirty build tree resulted in build failures
> > > > in arch/mips/kernel/signal.c:
> > > > 
> > > > arch/mips/kernel/signal.c: In function ‘sc_to_extcontext’:
> > > > arch/mips/kernel/signal.c:142:12: error: ‘struct ucontext’ has no member named ‘uc_extcontext’
> > > >   return &uc->uc_extcontext;
> > > >             ^
> > > > 
> > > > Fix by detecting and removing wrapper headers in generated header
> > > > directories that do not correspond to a filename in generic-y, genhdr-y,
> > > > or the newly introduced generated-y.
> > > 
> > > Good idea.
> > > 
> > > Acked-by: Arnd Bergmann <arnd@arndb.de>
> > 
> > Thanks Arnd
> > 
> > > Can you merge this through the mips tree, or do you need me to pick it
> > > up through asm-generic?
> > 
> > I was envisaging the kbuild tree tbh, but I don't really mind how it
> > gets merged. This patch depends on patch 1, which adds generated-y to
> > x86 so we don't delete their other generated headers, but other than
> > that it doesn't really have any dependencies.
> 
> Ok, the kbuild tree works fine too, and I guess the x86 tree would
> also be fine if that helps avoid the dependency.

Were you okay to take these patches, or would you prefer they go via the
MIPS tree?

Thanks
James

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2016-02-23  9:51 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-19 13:37 [PATCH v2 0/2] kbuild: Remove stale asm-generic wrappers James Hogan
2016-01-19 13:37 ` James Hogan
2016-01-19 13:37 ` [PATCH v2 2/2] " James Hogan
2016-01-19 13:37   ` James Hogan
2016-01-19 14:09   ` Arnd Bergmann
2016-01-19 14:09     ` Arnd Bergmann
2016-01-19 14:22     ` James Hogan
2016-01-19 14:22       ` James Hogan
2016-01-19 14:27       ` Arnd Bergmann
2016-02-23  9:51         ` James Hogan [this message]
2016-04-21 18:44           ` James Hogan
2016-04-21 18:44             ` James Hogan
2016-01-20 18:55   ` Florian Fainelli
2016-01-21  0:03   ` Paul Burton
2016-01-21  0:03     ` Paul Burton
2016-01-21 10:19     ` James Hogan
2016-01-21 10:19       ` James Hogan

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=20160223095107.GC21143@jhogan-linux.le.imgtec.org \
    --to=james.hogan@imgtec.com \
    --cc=arnd@arndb.de \
    --cc=f.fainelli@gmail.com \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@linux-mips.org \
    --cc=mmarek@suse.com \
    --cc=paul.burton@imgtec.com \
    --cc=ralf@linux-mips.org \
    --cc=xypron.glpk@gmx.de \
    /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).