mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Conor Dooley <conor.dooley@microchip.com>
Cc: 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,
	pavel@denx.de, jonathanh@nvidia.com, f.fainelli@gmail.com,
	sudipm.mukherjee@gmail.com, srw@sladewatkins.net, rwarsow@gmx.de,
	conor@kernel.org
Subject: Re: [PATCH 6.1 000/194] 6.1.47-rc1 review
Date: Wed, 23 Aug 2023 17:24:19 +0200	[thread overview]
Message-ID: <2023082308-obliged-protector-f04c@gregkh> (raw)
In-Reply-To: <20230823-washer-reemerge-a412d55f8214@wendy>

On Wed, Aug 23, 2023 at 10:35:54AM +0100, Conor Dooley wrote:
> On Mon, Aug 21, 2023 at 09:39:39PM +0200, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 6.1.47 release.
> > There are 194 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.
> 
> Fails to build for me with gcc-11/binutils 2.37 on RISC-V. The problematic
> patch is "riscv: Handle zicsr/zifencei issue between gcc and binutils".
> Can you drop that please, probably from all of your branches. It
> certainly affects 6.4 too & I don't personally test anything older than
> 6.1.

I've dropped that patch now from all trees, thanks.

greg k-h

      parent reply	other threads:[~2023-08-23 15:24 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-21 19:39 Greg Kroah-Hartman
2023-08-21 22:58 ` Joel Fernandes
2023-08-22 15:41   ` Joel Fernandes
2023-08-21 23:35 ` Takeshi Ogasawara
2023-08-22  3:00 ` Bagas Sanjaya
2023-08-22 10:55 ` Naresh Kamboju
2023-08-22 15:27   ` Salvatore Bonaccorso
2023-08-22 15:51     ` Greg Kroah-Hartman
2023-08-22 17:27       ` Greg Kroah-Hartman
2023-08-22 11:01 ` SeongJae Park
2023-08-22 14:08 ` Shuah Khan
2023-08-22 20:23 ` Florian Fainelli
2023-08-22 23:55 ` Ron Economos
2023-08-23  0:49 ` Guenter Roeck
2023-08-23  7:03   ` Greg Kroah-Hartman
2023-08-23  8:17     ` Naresh Kamboju
2023-08-23  8:27       ` Greg Kroah-Hartman
2023-08-23 13:30       ` Guenter Roeck
2023-08-23 15:50         ` Greg Kroah-Hartman
2023-08-24 13:35           ` Greg Kroah-Hartman
2023-08-24 15:08             ` Guenter Roeck
2023-08-24 15:15               ` Greg Kroah-Hartman
2023-08-24 15:58                 ` Guenter Roeck
2023-08-24 16:40                   ` Greg Kroah-Hartman
2023-08-23 13:28     ` Guenter Roeck
2023-08-23  8:54 ` Sudip Mukherjee (Codethink)
2023-08-23  9:26   ` Greg Kroah-Hartman
2023-08-23 10:32     ` Naresh Kamboju
2023-08-23 13:30       ` Guenter Roeck
2023-08-23 14:37     ` Sudip Mukherjee
2023-08-23  9:35 ` Conor Dooley
2023-08-23 13:37   ` Guenter Roeck
2023-08-23 15:24   ` Greg Kroah-Hartman [this message]

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=2023082308-obliged-protector-f04c@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=akpm@linux-foundation.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=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome