From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: open list <linux-kernel@vger.kernel.org>,
Shuah Khan <shuah@kernel.org>,
patches@kernelci.org, lkft-triage@lists.linaro.org,
linux-stable <stable@vger.kernel.org>,
pavel@denx.de, Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Guenter Roeck <linux@roeck-us.net>,
sagar.kadam@sifive.com, Palmer Dabbelt <palmerdabbelt@google.com>,
Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 5.4 00/88] 5.4.93-rc2 review
Date: Tue, 26 Jan 2021 12:16:56 +0100 [thread overview]
Message-ID: <YA/6KP4DNVkpSBA5@kroah.com> (raw)
In-Reply-To: <CA+G9fYtqJDKOwFGevaOmmK7gbKgo61CpL70yyG2daOxvRp5FSQ@mail.gmail.com>
On Tue, Jan 26, 2021 at 04:43:51PM +0530, Naresh Kamboju wrote:
> On Tue, 26 Jan 2021 at 15:33, Greg Kroah-Hartman
> <gregkh@linuxfoundation.org> wrote:
> >
> > This is the start of the stable review cycle for the 5.4.93 release.
> > There are 88 patches in this series, all will be posted as a response
> > to this one. If anyone has any issues with these being applied, please
> > let me know.
> >
> > Responses should be made by Thu, 28 Jan 2021 09:42:44 +0000.
> > Anything received after that time might be too late.
> >
> > The whole patch series can be found in one patch at:
> > https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.4.93-rc2.gz
> > or in the git tree and branch at:
> > git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-5.4.y
> > and the diffstat can be found below.
> >
> > thanks,
> >
> > greg k-h
>
> As Daniel pointed in the other email thread,
> riscv failed build:
> * clang-10-defconfig - FAILED
> * clang-11-defconfig - FAILED
> * gcc-8-defconfig - FAILED
> * gcc-9-defconfig - FAILED
> * gcc-10-defconfig - FAILED
>
> the riscv build failed due to the below commit.
>
> > Sagar Shrikant Kadam <sagar.kadam@sifive.com>
> > dts: phy: add GPIO number and active state used for phy reset
>
> make --silent --keep-going --jobs=8
> O=/home/tuxbuild/.cache/tuxmake/builds/1/tmp ARCH=riscv
> CROSS_COMPILE=riscv64-linux-gnu- 'CC=sccache riscv64-linux-gnu-gcc'
> 'HOSTCC=sccache gcc'
> arch/riscv/boot/dts/sifive/hifive-unleashed-a00.dts:88.27-28 syntax error
> FATAL ERROR: Unable to parse input tree
>
> Build log,
> https://gitlab.com/Linaro/lkft/mirrors/stable/linux-stable-rc/-/jobs/986616680
Crap, forgot that one. Will go drop it now and push out a -rc3. Is
this an issue for 5.10.y?
thanks,
greg k-h
next prev parent reply other threads:[~2021-01-26 11:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-26 10:03 [PATCH 5.4 00/88] 5.4.93-rc2 review Greg Kroah-Hartman
2021-01-26 11:13 ` Naresh Kamboju
2021-01-26 11:16 ` Greg Kroah-Hartman [this message]
2021-01-26 11:28 ` Naresh Kamboju
2021-01-26 12:21 ` Greg Kroah-Hartman
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=YA/6KP4DNVkpSBA5@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lkft-triage@lists.linaro.org \
--cc=naresh.kamboju@linaro.org \
--cc=palmerdabbelt@google.com \
--cc=patches@kernelci.org \
--cc=pavel@denx.de \
--cc=sagar.kadam@sifive.com \
--cc=sashal@kernel.org \
--cc=shuah@kernel.org \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.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