From: Boris Brezillon <boris.brezillon@free-electrons.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: gregkh <gregkh@linuxfoundation.org>,
"Olof Johansson" <olof@lixom.net>,
"Kernel Build Reports Mailman List"
<kernel-build-reports@lists.linaro.org>,
"Olof's autobuilder" <build@lixom.net>,
"# 3.18.x" <stable@vger.kernel.org>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Robert Jarzmik" <robert.jarzmik@free.fr>,
"Sean Nyekjær" <sean.nyekjaer@prevas.dk>,
"Ezequiel Garcia" <ezequiel@vanguardiasur.com.ar>
Subject: Re: stable-rc build: 0 warnings 5 failures (stable-rc/v3.18.91-23-g72813f7)
Date: Fri, 12 Jan 2018 12:02:10 +0100 [thread overview]
Message-ID: <20180112120210.00507bf7@bbrezillon> (raw)
In-Reply-To: <CAK8P3a2shHXN5S9OMYCnTKSo5V+H-TwSWBEa7hEZFd_4wUzf3Q@mail.gmail.com>
On Fri, 12 Jan 2018 11:57:55 +0100
Arnd Bergmann <arnd@arndb.de> wrote:
> On Fri, Jan 12, 2018 at 11:49 AM, Olof's autobuilder <build@lixom.net> wrote:
> > Here are the build results from automated periodic testing.
> >
> > The tree being built was stable-rc, found at:
> >
> > URL: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
>
> >
> > Errors:
> >
> > arm.allmodconfig:
> > /work/build/batch/drivers/mtd/nand/pxa3xx_nand.c:749:2: error: duplicate case value
> >
> > arm.cm_x300_defconfig:
> > /work/build/batch/drivers/mtd/nand/pxa3xx_nand.c:749:2: error: duplicate case value
> >
> > arm.mvebu_v7_defconfig:
> > /work/build/batch/drivers/mtd/nand/pxa3xx_nand.c:749:2: error: duplicate case value
> >
> > arm.pxa3xx_defconfig:
> > /work/build/batch/drivers/mtd/nand/pxa3xx_nand.c:749:2: error: duplicate case value
> >
> > arm.raumfeld_defconfig:
> > /work/build/batch/drivers/mtd/nand/pxa3xx_nand.c:749:2: error: duplicate case value
>
> Same problem as with 4.4.y before:
>
> fee4380f368e ("mtd: nand: pxa3xx: Fix READOOB implementation")
>
> was backported as commit fea22562533e but needs to be done differently here.
It should just be dropped (the bug is not present on pre-4.6 kernels).
Sorry for messing up with the Fixes tag, which led to this
situation :-/.
next prev parent reply other threads:[~2018-01-12 11:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5a5892bd.0a13620a.19727.383f@mx.google.com>
2018-01-12 10:57 ` stable-rc build: 0 warnings 5 failures (stable-rc/v3.18.91-23-g72813f7) Arnd Bergmann
2018-01-12 11:02 ` Boris Brezillon [this message]
2018-01-13 10:09 ` gregkh
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=20180112120210.00507bf7@bbrezillon \
--to=boris.brezillon@free-electrons.com \
--cc=arnd@arndb.de \
--cc=build@lixom.net \
--cc=ezequiel@vanguardiasur.com.ar \
--cc=gregkh@linuxfoundation.org \
--cc=kernel-build-reports@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olof@lixom.net \
--cc=robert.jarzmik@free.fr \
--cc=sean.nyekjaer@prevas.dk \
--cc=stable@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.