From: Max Filippov <jcmvbkbc@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: kernel test robot <lkp@intel.com>,
kbuild-all@lists.01.org, LKML <linux-kernel@vger.kernel.org>,
Sasha Levin <sashal@kernel.org>
Subject: Re: [linux-stable-rc:linux-4.19.y 565/981] arch/xtensa/platforms/xtfpga/include/platform/hardware.h:50:33: error: initializer element is not constant
Date: Mon, 29 Nov 2021 05:00:55 -0800 [thread overview]
Message-ID: <CAMo8BfKSaOUD5V5G+PBaLqcmcVnHw=JwrYP=hoLRoNj=oWDdLw@mail.gmail.com> (raw)
In-Reply-To: <YaN+E5fuvU2VO+W5@kroah.com>
Hi Greg,
On Sun, Nov 28, 2021 at 5:03 AM Greg Kroah-Hartman
<gregkh@linuxfoundation.org> wrote:
> On Sat, Nov 27, 2021 at 07:10:56AM -0800, Max Filippov wrote:
> > This happens because the backported change
> > 1c21a8df144f1edb3b6f5f24559825780c227a7d depends on the change
> > d67ed2510d28 ("xtensa: use CONFIG_USE_OF instead of CONFIG_OF")
> > which is not in that stable tree.
> >
> > Should I send the backported version of the d67ed2510d28 or should
> > the change 1c21a8df144f1edb3b6f5f24559825780c227a7d be reverted
> > from the stable? (IMO they are not the stable material).
>
> I have queued up d67ed2510d28 ("xtensa: use CONFIG_USE_OF instead of
> CONFIG_OF") to hopefully resolve this.
Thank you. However the change that you've queued is missing one
hunk of the original patch that makes the difference in this case.
I guess it's missing due to conflict introduced by the change
6591685d5004 ("xtensa: move XCHAL_KIO_* definitions to kmem_layout.h")
I've posted another backported version of this patch that includes
that missing part. Could you please apply it instead?
--
Thanks.
-- Max
next prev parent reply other threads:[~2021-11-29 14:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-27 2:32 [linux-stable-rc:linux-4.19.y 565/981] arch/xtensa/platforms/xtfpga/include/platform/hardware.h:50:33: error: initializer element is not constant kernel test robot
2021-11-27 15:10 ` Max Filippov
2021-11-28 13:03 ` Greg Kroah-Hartman
2021-11-29 13:00 ` Max Filippov [this message]
2021-11-29 13:14 ` 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='CAMo8BfKSaOUD5V5G+PBaLqcmcVnHw=JwrYP=hoLRoNj=oWDdLw@mail.gmail.com' \
--to=jcmvbkbc@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=sashal@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 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).