From: Jisheng.Zhang@synaptics.com (Jisheng Zhang)
To: linux-arm-kernel@lists.infradead.org
Subject: [4.14.y] request commit 94a5d8790e79 ("arm64: cpu_errata: include required headers")
Date: Thu, 13 Sep 2018 15:33:50 +0800 [thread overview]
Message-ID: <20180913153350.0adc1c48@xhacker.debian> (raw)
In-Reply-To: <20180913152420.6c6324f4@xhacker.debian>
On Thu, 13 Sep 2018 15:24:20 +0800 Jisheng Zhang wrote:
> Hi Greg,
>
> On Thu, 13 Sep 2018 09:12:16 +0200 Greg Kroah-Hartman wrote:
>
> > On Tue, Sep 11, 2018 at 05:00:30PM +0800, Jisheng Zhang wrote:
> > > Hi Greg,
> > >
> > > I think we missed the commit 94a5d8790e79 ("arm64: cpu_errata: include
> > > required headers"), could you please include it in next stable release?
> >
> > Really, you are seeing build failures on 4.14.y without this patch
> > applied? I haven't gotten any reports of this, what is wrong with our
>
> yes. I see similar build errors as the commit mentioned. Per my test, setting
> CONFIG_ARM64_SSBD as y will trigger the errors.
hmm, it looks like the defconfig in arch/arm64/configs can't trigger the
build errors. But my version could, I attach it for reference.
>
> Thanks
>
> > build tests that this isn't being caught?
> >
> > thanks,
> >
> > greg k-h
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: config_bad.gz
Type: application/gzip
Size: 12599 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20180913/df4b8b49/attachment-0001.gz>
next prev parent reply other threads:[~2018-09-13 7:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-11 9:00 [4.14.y] request commit 94a5d8790e79 ("arm64: cpu_errata: include required headers") Jisheng Zhang
2018-09-13 7:12 ` Greg Kroah-Hartman
2018-09-13 7:24 ` Jisheng Zhang
2018-09-13 7:33 ` Jisheng Zhang [this message]
2018-09-13 7:38 ` Greg Kroah-Hartman
2018-09-13 7:40 ` Arnd Bergmann
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=20180913153350.0adc1c48@xhacker.debian \
--to=jisheng.zhang@synaptics.com \
--cc=linux-arm-kernel@lists.infradead.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).