public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Wang Yugui <wangyugui@e16-tech.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
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, allen.lkml@gmail.com, broonie@kernel.org
Subject: Re: [PATCH 6.6 000/744] 6.6.33-rc1 review
Date: Fri, 07 Jun 2024 15:25:06 +0800	[thread overview]
Message-ID: <20240607152504.4D97.409509F4@e16-tech.com> (raw)
In-Reply-To: <20240606131732.440653204@linuxfoundation.org>

Hi,

> This is the start of the stable review cycle for the 6.6.33 release.
> There are 744 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 Sat, 08 Jun 2024 13:15:55 +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.6.33-rc1.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.6.y
> and the diffstat can be found below.

To build the 6.6.33-rc1 successfully on x86_64, we need the following 2 patches.

8a55c1e2c9e1 perf util: Add a function for replacing characters in a string
f6ff1c760431 perf evlist: Add perf_evlist__go_system_wide() helper

Best Regards
Wang Yugui (wangyugui@e16-tech.com)
2024/06/07



  parent reply	other threads:[~2024-06-07  7:56 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-06 13:54 [PATCH 6.6 000/744] 6.6.33-rc1 review Greg Kroah-Hartman
2024-06-06 14:01 ` [PATCH 6.6 442/744] coresight: etm4x: Fix unbalanced pm_runtime_enable() Greg Kroah-Hartman
2024-06-06 14:28 ` [PATCH 6.6 000/744] 6.6.33-rc1 review Naresh Kamboju
2024-06-06 17:53 ` SeongJae Park
2024-06-06 21:53 ` Shuah Khan
2024-06-07  7:25 ` Wang Yugui [this message]
2024-06-09 11:16   ` Greg Kroah-Hartman
2024-06-07  9:02 ` Jon Hunter
2024-06-07 10:52 ` Naresh Kamboju
2024-06-07 11:33 ` Takeshi Ogasawara
2024-06-07 15:23 ` Conor Dooley
2024-06-07 15:26   ` Greg Kroah-Hartman
2024-06-07 15:54     ` Conor Dooley
2024-06-07 15:24 ` Mark Brown
2024-06-07 18:02 ` Allen
2024-06-07 21:30 ` Ron Economos

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=20240607152504.4D97.409509F4@e16-tech.com \
    --to=wangyugui@e16-tech.com \
    --cc=akpm@linux-foundation.org \
    --cc=allen.lkml@gmail.com \
    --cc=broonie@kernel.org \
    --cc=conor@kernel.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=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