public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Jon Hunter <jonathanh@nvidia.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, f.fainelli@gmail.com, sudipm.mukherjee@gmail.com,
	srw@sladewatkins.net, rwarsow@gmx.de, conor@kernel.org,
	allen.lkml@gmail.com, broonie@kernel.org,
	"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>
Subject: Re: [PATCH 6.1 000/798] 6.1.113-rc1 review
Date: Tue, 15 Oct 2024 13:18:47 +0200	[thread overview]
Message-ID: <2024101532-evolve-only-5844@gregkh> (raw)
In-Reply-To: <6a357a0c-2cbf-4205-955b-5f2866ba7829@nvidia.com>

On Tue, Oct 15, 2024 at 06:50:43AM +0100, Jon Hunter wrote:
> 
> On 15/10/2024 06:31, Jon Hunter wrote:
> > Hi Greg,
> > 
> > On 14/10/2024 15:09, Greg Kroah-Hartman wrote:
> > > This is the start of the stable review cycle for the 6.1.113 release.
> > > There are 798 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, 16 Oct 2024 14:09:57 +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.1.113-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.1.y
> > > and the diffstat can be found below.
> > > 
> > > thanks,
> > > 
> > > greg k-h
> > > 
> > > -------------
> > > Pseudo-Shortlog of commits:
> > 
> > ...
> > 
> > > Oleksij Rempel <linux@rempel-privat.de>
> > >      clk: imx6ul: add ethernet refclock mux support
> > 
> > 
> > I am seeing the following build issue for ARM multi_v7_defconfig and
> > bisect is point to the commit ...
> 
> To be clear, I meant the 'above' commit.

Thanks, let me go drop this (and the other ones around it) and push out
some -rc2 releases.

greg k-h

  reply	other threads:[~2024-10-15 11:18 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-14 14:09 [PATCH 6.1 000/798] 6.1.113-rc1 review Greg Kroah-Hartman
2024-10-14 14:19 ` [PATCH 6.1 624/798] arm64: Add Cortex-715 CPU part definition Greg Kroah-Hartman
2024-10-14 14:20 ` [PATCH 6.1 654/798] erofs: get rid of erofs_inode_datablocks() Greg Kroah-Hartman
2024-10-14 14:20 ` [PATCH 6.1 655/798] erofs: get rid of z_erofs_do_map_blocks() forward declaration Greg Kroah-Hartman
2024-10-14 14:20 ` [PATCH 6.1 656/798] erofs: avoid hardcoded blocksize for subpage block support Greg Kroah-Hartman
2024-10-14 14:20 ` [PATCH 6.1 657/798] erofs: set block size to the on-disk block size Greg Kroah-Hartman
2024-10-14 14:20 ` [PATCH 6.1 658/798] erofs: fix incorrect symlink detection in fast symlink Greg Kroah-Hartman
2024-10-14 14:20 ` [PATCH 6.1 672/798] perf lock: Dynamically allocate lockhash_table Greg Kroah-Hartman
2024-10-14 20:35 ` [PATCH 6.1 000/798] 6.1.113-rc1 review Florian Fainelli
2024-10-15  3:43 ` Peter Schneider
2024-10-15  5:31 ` Jon Hunter
2024-10-15  5:50   ` Jon Hunter
2024-10-15 11:18     ` Greg Kroah-Hartman [this message]
2024-10-15  6:29   ` Pavel Machek
2024-10-15  7:06   ` Geert Uytterhoeven
2024-10-15  7:07     ` Geert Uytterhoeven
2024-10-15  9:38       ` Oleksij Rempel
2024-10-15  7:47 ` Naresh Kamboju
2024-10-15  8:53 ` Naresh Kamboju
2024-10-15  9:50   ` Heiko Carstens
2024-10-15 11:14     ` Greg Kroah-Hartman
2024-10-15 14:40 ` Shuah Khan

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=2024101532-evolve-only-5844@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=akpm@linux-foundation.org \
    --cc=allen.lkml@gmail.com \
    --cc=broonie@kernel.org \
    --cc=conor@kernel.org \
    --cc=f.fainelli@gmail.com \
    --cc=jonathanh@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@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