All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Guenter Roeck <linux@roeck-us.net>
Cc: stable@vger.kernel.org, patches@lists.linux.dev,
	linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
	akpm@linux-foundation.org, 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/741] 6.6.33-rc2 review
Date: Tue, 18 Jun 2024 15:18:07 +0200	[thread overview]
Message-ID: <2024061855-rural-stoplight-1283@gregkh> (raw)
In-Reply-To: <55b8c260-d8f0-4c05-bdf1-c20865fb13f7@roeck-us.net>

On Mon, Jun 17, 2024 at 10:38:29AM -0700, Guenter Roeck wrote:
> Hi,
> 
> On 6/9/24 04:41, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 6.6.33 release.
> > There are 741 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 Tue, 11 Jun 2024 11:36:08 +0000.
> > Anything received after that time might be too late.
> > 
> [ ... ]
> > 
> > Duanqiang Wen <duanqiangwen@net-swift.com>
> >      Revert "net: txgbe: fix clk_name exceed MAX_DEV_ID limits"
> > 
> 
> This patch, in its commit message, explicitly states:
> 
>   This reverts commit e30cef001da259e8df354b813015d0e5acc08740.
>   commit 99f4570cfba1 ("clkdev: Update clkdev id usage to allow
>   for longer names") can fix clk_name exceed MAX_DEV_ID limits,
>   so this commit is meaningless.
> 
> However, commit 99f4570cfba1 has not been applied to v6.6.y,
> meaning the revert may impact the affected driver under some
> circumstances.

Ah, that was tricky, thanks, I've queued up 99f4570cfba1 now.

greg k-h

      reply	other threads:[~2024-06-18 13:20 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-09 11:41 [PATCH 6.6 000/741] 6.6.33-rc2 review Greg Kroah-Hartman
2024-06-09 13:25 ` Takeshi Ogasawara
2024-06-09 16:11 ` SeongJae Park
2024-06-09 19:34 ` Pavel Machek
2024-06-10  6:21   ` Ron Economos
2024-06-10  6:28     ` Greg Kroah-Hartman
2024-06-10  7:26       ` Conor Dooley
2024-06-11 13:06         ` Greg Kroah-Hartman
2024-06-19 14:28           ` Conor Dooley
2024-06-19 14:48             ` Greg Kroah-Hartman
2024-06-10  9:43   ` Naresh Kamboju
2024-06-10  9:56 ` Jon Hunter
2024-06-10 14:20 ` Mark Brown
2024-06-10 15:26 ` Shreeya Patel
2024-06-10 17:55 ` Naresh Kamboju
2024-06-11  4:01 ` Kelsey Steele
2024-06-17 17:38 ` Guenter Roeck
2024-06-18 13:18   ` 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=2024061855-rural-stoplight-1283@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@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.