public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Fox Chen <foxhlchen@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	stable@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, slade@sladewatkins.com,
	Fox Chen <foxhlchen@gmail.com>
Subject: RE: [PATCH 5.15 000/256] 5.15.27-rc2 review
Date: Mon, 07 Mar 2022 18:31:05 -0800 (PST)	[thread overview]
Message-ID: <6226bfe9.1c69fb81.aca0a.45f8@mx.google.com> (raw)
In-Reply-To: <20220307162207.188028559@linuxfoundation.org>

On Mon,  7 Mar 2022 17:28:50 +0100, Greg Kroah-Hartman <gregkh@linuxfoundation.org> wrote:
> This is the start of the stable review cycle for the 5.15.27 release.
> There are 256 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 Wed, 09 Mar 2022 16:21:31 +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/v5.x/stable-review/patch-5.15.27-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-5.15.y
> and the diffstat can be found below.
> 
> thanks,
> 
> greg k-h
> 

5.15.27-rc2 Successfully Compiled and booted on my Raspberry PI 4b (8g) (bcm2711)
                
Tested-by: Fox Chen <foxhlchen@gmail.com>


  parent reply	other threads:[~2022-03-08  2:31 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-07 16:28 [PATCH 5.15 000/256] 5.15.27-rc2 review Greg Kroah-Hartman
2022-03-07 19:41 ` Florian Fainelli
2022-03-07 23:49 ` Shuah Khan
     [not found]   ` <CADo9pHjuByLte3d8WhKf1jWw_=EoW-76405ptW-sZg0-AakxqQ@mail.gmail.com>
     [not found]     ` <CADo9pHiJGXFwvXDRqRCjYqowJkkP3GYzkO8jqPQK=z71V_5FOw@mail.gmail.com>
2022-03-08 15:48       ` Greg Kroah-Hartman
2022-03-08  2:31 ` Fox Chen [this message]
2022-03-08  7:49 ` Naresh Kamboju
2022-03-08  9:06 ` Ron Economos
2022-03-08 13:35 ` Bagas Sanjaya
2022-03-08 15:36 ` Sudip Mukherjee
2022-03-08 16:09   ` Sudip Mukherjee
2022-03-08 17:38     ` Naresh Kamboju
2022-03-08 21:05       ` Greg Kroah-Hartman
2022-03-08 22:27         ` Sudip Mukherjee
2022-03-09  0:53           ` Guenter Roeck
2022-03-09  9:53             ` Sudip Mukherjee
2022-03-09 11:58               ` Greg Kroah-Hartman
2022-03-08 22:45         ` Guenter Roeck
2022-03-09 11:57           ` 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=6226bfe9.1c69fb81.aca0a.45f8@mx.google.com \
    --to=foxhlchen@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=f.fainelli@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --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=pavel@denx.de \
    --cc=shuah@kernel.org \
    --cc=slade@sladewatkins.com \
    --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