All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Conor Dooley <conor@kernel.org>
Cc: Conor Dooley <conor.dooley@microchip.com>,
	Ron Economos <re@w6rz.net>, Pavel Machek <pavel@denx.de>,
	stable@vger.kernel.org, patches@lists.linux.dev,
	linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
	akpm@linux-foundation.org, linux@roeck-us.net, shuah@kernel.org,
	patches@kernelci.org, lkft-triage@lists.linaro.org,
	jonathanh@nvidia.com, f.fainelli@gmail.com,
	sudipm.mukherjee@gmail.com, srw@sladewatkins.net, rwarsow@gmx.de,
	allen.lkml@gmail.com, broonie@kernel.org
Subject: Re: [PATCH 6.6 000/741] 6.6.33-rc2 review
Date: Wed, 19 Jun 2024 16:48:35 +0200	[thread overview]
Message-ID: <2024061905-reclining-discount-996d@gregkh> (raw)
In-Reply-To: <20240619-kerchief-grove-20c3996db1aa@spud>

On Wed, Jun 19, 2024 at 03:28:18PM +0100, Conor Dooley wrote:
> On Tue, Jun 11, 2024 at 03:06:01PM +0200, Greg Kroah-Hartman wrote:
> > On Mon, Jun 10, 2024 at 08:26:10AM +0100, Conor Dooley wrote:
> > > On Mon, Jun 10, 2024 at 08:28:29AM +0200, Greg Kroah-Hartman wrote:
> > > > On Sun, Jun 09, 2024 at 11:21:55PM -0700, Ron Economos wrote:
> > > > > On 6/9/24 12:34 PM, Pavel Machek wrote:
> > > > > > Hi!
> > > > > > 
> > > > > > > This is the start of the stable review cycle for the 6.6.33 release.
> > > > > > > There are 741 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.
> > > > > > 6.6 seems to have build problem on risc-v:
> > > 
> > > > > > arch/riscv/kernel/suspend.c:14:66: error: 'RISCV_ISA_EXT_XLINUXENVCFG' undeclared (first use in this function); did you mean 'RISCV_ISA_EXT_ZIFENCEI'?
> > > > > > 694
> > > > > >     14 |         if (riscv_cpu_has_extension_unlikely(smp_processor_id(), RISCV_ISA_EXT_XLINUXENVCFG))
> > > > > > 695
> > > > > >        |                                                                  ^~~~~~~~~~~~~~~~~~~~~~~~~~
> > > > > > 696
> > > > > >        |                                                                  RISCV_ISA_EXT_ZIFENCEI
> > > 
> > > > > > https://gitlab.com/cip-project/cip-testing/linux-stable-rc-ci/-/jobs/7053222239
> > > > > > https://gitlab.com/cip-project/cip-testing/linux-stable-rc-ci/-/pipelines/1324369118
> > > > > > 
> > > > > > No problems detected on 6.8-stable and 6.1-stable.
> > > > > > 
> > > > > > Best regards,
> > > > > > 								Pavel
> > > > > 
> > > > > I'm seeing the same thing here. Somehow some extra patches got slipped in
> > > > > between rc1 and rc2. The new patches for RISC-V are:
> > > > > 
> > > > > Samuel Holland <samuel.holland@sifive.com>
> > > > >     riscv: Save/restore envcfg CSR during CPU suspend
> > > > > 
> > > > > commit 88b55a586b87994a33e0285c9e8881485e9b77ea
> > > > > 
> > > > > Samuel Holland <samuel.holland@sifive.com>
> > > > >     riscv: Fix enabling cbo.zero when running in M-mode
> > > > > 
> > > > > commit 8c6e096cf527d65e693bfbf00aa6791149c58552
> > > > > 
> > > > > The first patch "riscv: Save/restore envcfg CSR during CPU suspend" causes
> > > > > the build failure.
> > > > > 
> > > > > 
> > > > 
> > > > Yes, these were added because they were marked as fixes for other
> > > > commits in the series.  I'll unwind them all now as something is going
> > > > wrong...
> > > 
> > > Really we should just backport this envcfg handling to stable, this
> > > isn't the first (and won't be the last) issue it'll cause. I'll put a
> > > backport of it on my todo list cos I think last time around it couldn't
> > > be cherrypicked.
> > 
> > Thanks, I've dropped almost all riscv patches from this queue now.  If
> > they want to be added back, please send working backports :)
> 
> I went to take a look at this, but since 6.8 is now EOL, I dunno if I
> actually need to do anything here? These were needed because you had
> applied "RISC-V: Enable cbo.zero in usermode", but that's a feature, not
> a fix, so dropping that makes these changes unneeded. IIRC the previous
> time that there was an envcfg related build failure it was on the
> requested backport to 6.7+ in the envcfg addition in "riscv: Add a custom
> ISA extension for the [ms]envcfg CSR", and an assertion failed because
> of a definition for the maximum number of ISA extensions was larger in
> 6.9 than 6.7 and the patch depended on that.

Yes, 6.8.y is end-of-life, nothing needs to be done there anymore.

> For 6.6, I don't think envcfg is needed, unless there was some other
> reason that you backported "RISC-V: Enable cbo.zero in usermode".

I hope not :)

thanks for looking.

greg k-h

  reply	other threads:[~2024-06-19 14:48 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-09 11:41 [PATCH 6.6 000/741] 6.6.33-rc2 review Greg Kroah-Hartman
2024-06-09 13:25 ` Takeshi Ogasawara
2024-06-09 16:11 ` SeongJae Park
2024-06-09 19:34 ` Pavel Machek
2024-06-10  6:21   ` Ron Economos
2024-06-10  6:28     ` Greg Kroah-Hartman
2024-06-10  7:26       ` Conor Dooley
2024-06-11 13:06         ` Greg Kroah-Hartman
2024-06-19 14:28           ` Conor Dooley
2024-06-19 14:48             ` Greg Kroah-Hartman [this message]
2024-06-10  9:43   ` Naresh Kamboju
2024-06-10  9:56 ` Jon Hunter
2024-06-10 14:20 ` Mark Brown
2024-06-10 15:26 ` Shreeya Patel
2024-06-10 17:55 ` Naresh Kamboju
2024-06-11  4:01 ` Kelsey Steele
2024-06-17 17:38 ` Guenter Roeck
2024-06-18 13:18   ` 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=2024061905-reclining-discount-996d@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=akpm@linux-foundation.org \
    --cc=allen.lkml@gmail.com \
    --cc=broonie@kernel.org \
    --cc=conor.dooley@microchip.com \
    --cc=conor@kernel.org \
    --cc=f.fainelli@gmail.com \
    --cc=jonathanh@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=lkft-triage@lists.linaro.org \
    --cc=patches@kernelci.org \
    --cc=patches@lists.linux.dev \
    --cc=pavel@denx.de \
    --cc=re@w6rz.net \
    --cc=rwarsow@gmx.de \
    --cc=shuah@kernel.org \
    --cc=srw@sladewatkins.net \
    --cc=stable@vger.kernel.org \
    --cc=sudipm.mukherjee@gmail.com \
    --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 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.