mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: <Conor.Dooley@microchip.com>
To: <gregkh@linuxfoundation.org>, <stable@vger.kernel.org>, <hi@alyssa.is>
Cc: <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>
Subject: Re: [PATCH 6.2 000/138] 6.2.12-rc2 review
Date: Wed, 19 Apr 2023 12:26:26 +0000	[thread overview]
Message-ID: <b6e0cc8b-eb4b-4906-9697-a1dab4741745@microchip.com> (raw)
In-Reply-To: <20230419093655.693770727@linuxfoundation.org>

On 19/04/2023 10:40, Greg Kroah-Hartman wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
> 
> This is the start of the stable review cycle for the 6.2.12 release.
> There are 138 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 Fri, 21 Apr 2023 09:36:26 +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/v6.x/stable-review/patch-6.2.12-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-6.2.y
> and the diffstat can be found below.
> 
> thanks,
> 
> greg k-h


> Alyssa Ross <hi@alyssa.is>
>      purgatory: fix disabling debug info
> 
> Heiko Stuebner <heiko.stuebner@vrull.eu>
>      RISC-V: add infrastructure to allow different str* implementations

Lore is ~dead for me right now, but there should be a custom backport of
Alyssa's commit, submitted by her, here:
https://lore.kernel.org/all/20230417134044.1821014-1-hi@alyssa.is/

Perhaps the reason is just the quantity of email, but that was
submitted against the "fail" email (and within a few hours), so why
was another commit pulled back instead of using what she provided?


> Alexandre Ghiti <alexghiti@rivosinc.com>
>      riscv: Do not set initial_boot_params to the linear address of the dtb

Same as 6.1.y, Alex said he'll provide a backport for the whole
series, so just drop this here too please.

Thanks,
Conor.

  reply	other threads:[~2023-04-19 12:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-19  9:40 Greg Kroah-Hartman
2023-04-19 12:26 ` Conor.Dooley [this message]
2023-04-19 13:17   ` Greg KH
2023-04-19 13:57     ` Alyssa Ross
2023-04-19 14:54       ` Greg KH

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=b6e0cc8b-eb4b-4906-9697-a1dab4741745@microchip.com \
    --to=conor.dooley@microchip.com \
    --cc=akpm@linux-foundation.org \
    --cc=f.fainelli@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=hi@alyssa.is \
    --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

all inboxes | Powered by JetHome®