From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Arend van Spriel <arend.vanspriel@broadcom.com>
Cc: "Arnd Bergmann" <arnd@arndb.de>,
"Rafał Miłecki" <zajec5@gmail.com>,
"Brian Norris" <computersforpeace@gmail.com>,
linux-mtd <linux-mtd@lists.infradead.org>,
linux-wireless <linux-wireless@vger.kernel.org>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"open list:RALINK MIPS ARCHITECTURE" <linux-mips@linux-mips.org>,
"Ingo Molnar" <mingo@kernel.org>
Subject: Re: [PATCH] bcm47xx: fix build regression
Date: Thu, 1 Jun 2017 15:16:32 -0700 [thread overview]
Message-ID: <20170601221632.GH3956@linux.vnet.ibm.com> (raw)
In-Reply-To: <51fbd3af-853e-f055-bef5-58d7438ba1ae@broadcom.com>
On Wed, May 31, 2017 at 09:30:19PM +0200, Arend van Spriel wrote:
> On 31-05-17 18:31, Paul E. McKenney wrote:
> > On Wed, May 31, 2017 at 03:34:57PM +0200, Arnd Bergmann wrote:
> >> On Wed, May 31, 2017 at 3:12 PM, Paul E. McKenney
> >> <paulmck@linux.vnet.ibm.com> wrote:
> >>> On Wed, May 31, 2017 at 12:21:10PM +0200, Arnd Bergmann wrote:
> >>>> On Wed, May 31, 2017 at 11:43 AM, Arend van Spriel
> >>>> <arend.vanspriel@broadcom.com> wrote:
> >>>>> On 5/30/2017 1:20 PM, Arnd Bergmann wrote:
> >>>>>>
> >>>>>> An unknown change in the kernel headers caused a build regression
> >>>>>> in an MTD partition driver:
> >>>>>>
> >>>>>> In file included from drivers/mtd/bcm47xxpart.c:12:0:
> >>>>>> include/linux/bcm47xx_nvram.h: In function 'bcm47xx_nvram_init_from_mem':
> >>>>>> include/linux/bcm47xx_nvram.h:27:10: error: 'ENOTSUPP' undeclared (first
> >>>>>> use in this function)
> >>>>>>
> >>>>>> Clearly we want to include linux/errno.h here.
> >>>>>
> >>>>>
> >>>>> unfortunate that you did not find the commit that caused this build
> >>>>> regression. You could produce preprocessor output when it was working to see
> >>>>> where errno.h got implicitly included and start looking there for git
> >>>>> history.
> >>>>
> >>>> I did a 'git bisect run make drivers/mtd/bcm47xxpart.o' now, which pointed to
> >>>> 0bc2d534708b ("rcu: Refactor #includes from include/linux/rcupdate.h").
> >>>>
> >>>> That commit seems reasonable, it was just bad luck that it caused this
> >>>> regression. The commit is currently in the rcu/rcu/next branch of tip.git,
> >>>> so Paul could merge the patch there.
>
> Arnd,
>
> Thanks for digging a bit further. I am a sucker for telling the whole story.
>
> >>>
> >>> Apologies for the inconvenience, not sure why 0day test robot didn't
> >>> find this. Probably because it cannot test each and every driver. ;-)
> >>
> >> No worries.
> >>
> >>> This patch, correct?
> >>>
> >>> https://lkml.org/lkml/2017/5/30/348
> >>
> >> Right, I should have included the link.
> >
> > And my turn to say "no worries". ;-)
> >
> > I reworked the commit log to tell the full story as shown below.
> > Anything I misstated or otherwise missed?
>
> Maybe add the 'Fixes:' tag, ie.:
>
> Fixes: 0bc2d534708b ("rcu: Refactor #includes from
> include/linux/rcupdate.h")
>
> Seems a bit redundant given that you mentioned it in the commit message,
> but it might be looked for in kernel-stats scripts.
Had to rebase anyway for other reasons, so why not?
Thanx, Paul
> Regards,
> Arend
>
> > Thanx, Paul
> >
> > ------------------------------------------------------------------------
> >
> > commit ff278071dce9af9da2b5e2b33f682710a855d266
> > Author: Arnd Bergmann <arnd@arndb.de>
> > Date: Wed May 31 09:26:07 2017 -0700
> >
> > bcm47xx: fix build regression
> >
> > Commit 0bc2d534708b ("rcu: Refactor #includes from include/linux/rcupdate.h")
> > caused a build regression in an MTD partition driver:
> >
> > In file included from drivers/mtd/bcm47xxpart.c:12:0:
> > include/linux/bcm47xx_nvram.h: In function 'bcm47xx_nvram_init_from_mem':
> > include/linux/bcm47xx_nvram.h:27:10: error: 'ENOTSUPP' undeclared (first use in this function)
> >
> > The rcupdate.h file has no particular need for linux/errno.h, so this
> > commit includes linux/errno.h into bcm47xx_nvram.h.
> >
> > Signed-off-by: Arnd Bergmann <arnd@arndb.de>
> > Signed-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
> >
> > diff --git a/include/linux/bcm47xx_nvram.h b/include/linux/bcm47xx_nvram.h
> > index 2793652fbf66..a414a2b53e41 100644
> > --- a/include/linux/bcm47xx_nvram.h
> > +++ b/include/linux/bcm47xx_nvram.h
> > @@ -8,6 +8,7 @@
> > #ifndef __BCM47XX_NVRAM_H
> > #define __BCM47XX_NVRAM_H
> >
> > +#include <linux/errno.h>
> > #include <linux/types.h>
> > #include <linux/kernel.h>
> > #include <linux/vmalloc.h>
> >
>
prev parent reply other threads:[~2017-06-01 22:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-30 11:20 [PATCH] bcm47xx: fix build regression Arnd Bergmann
2017-05-31 9:15 ` Boris Brezillon
2017-05-31 9:43 ` Arend van Spriel
2017-05-31 10:21 ` Arnd Bergmann
2017-05-31 13:12 ` Paul E. McKenney
2017-05-31 13:34 ` Arnd Bergmann
2017-05-31 16:31 ` Paul E. McKenney
2017-05-31 19:30 ` Arend van Spriel
2017-06-01 22:16 ` Paul E. McKenney [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=20170601221632.GH3956@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=arend.vanspriel@broadcom.com \
--cc=arnd@arndb.de \
--cc=computersforpeace@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=zajec5@gmail.com \
/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).