mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Wentao Guan <guanwentao@uniontech.com>
Cc: pschneider1968@googlemail.com, achill@achill.org,
	akpm@linux-foundation.org, broonie@kernel.org, conor@kernel.org,
	f.fainelli@gmail.com, hargar@microsoft.com, jonathanh@nvidia.com,
	linux-kernel@vger.kernel.org, linux@roeck-us.net,
	lkft-triage@lists.linaro.org, patches@kernelci.org,
	patches@lists.linux.dev, pavel@nabladev.com, rwarsow@gmx.de,
	shuah@kernel.org, sr@sladewatkins.com, stable@vger.kernel.org,
	sudipm.mukherjee@gmail.com, torvalds@linux-foundation.org
Subject: Re: [PATCH 6.18 0000/1518] 6.18.52-rc1 review
Date: Mon, 14 Sep 2026 11:38:09 +0200	[thread overview]
Message-ID: <2026091451-gauging-grumbly-41dc@gregkh> (raw)
In-Reply-To: <20260912220531.858986-1-guanwentao@uniontech.com>

On Sun, Sep 13, 2026 at 06:05:31AM +0800, Wentao Guan wrote:
> Hi,
> 
> > Am 12.09.2026 um 08:36 schrieb Greg Kroah-Hartman:
> > > This is the start of the stable review cycle for the 6.18.52 release.
> > > There are 1518 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.
> > 
> > Builds, boots and seems to works on my 2-socket Ivy Bridge Xeon E5-2697v2 server.
> > However, I do see the same strange dmesg warnings that I see in 6.12.110-rc1:
> > 
> > [    2.397237] Driver 'sr' needs updating - please use bus_type methods
> > ...
> > [   84.031323] Driver 'ses' needs updating - please use bus_type methods
> >
> > And again, these warning are new in this rc, they did not appear in 6.18.51.
> 
> Thanks for your report, i see the warning is related to the commit series:
> ("scsi: core: sysfs: Make use of bus callbacks")
> ... As it message describe ...
>     .probe(), .remove() and .shutdown() to eventually remove these. Until
>     all SCSI drivers are converted, this results in a runtime warning about
>     the drivers needing an update because there is a bus probe function and
>     a driver probe function. The in-tree drivers are fixed by the following
>     commits.
> ...

Yeah, that's a mess, I'll go drop this from 6.18 and 6.12 queues for
now, thanks for the review!

greg k-h

  reply	other threads:[~2026-09-14  9:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-12  6:36 Greg Kroah-Hartman
2026-09-12 10:37 ` Brett A C Sheffield
2026-09-12 17:33 ` Peter Schneider
2026-09-12 22:05   ` Wentao Guan
2026-09-14  9:38     ` Greg KH [this message]
2026-09-12 20:28 ` Wentao Guan
2026-09-13 17:21 ` Barry K. Nathan
2026-09-13 22:50 ` Ron Economos
2026-09-14  5:14 ` Miguel Ojeda

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=2026091451-gauging-grumbly-41dc@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=achill@achill.org \
    --cc=akpm@linux-foundation.org \
    --cc=broonie@kernel.org \
    --cc=conor@kernel.org \
    --cc=f.fainelli@gmail.com \
    --cc=guanwentao@uniontech.com \
    --cc=hargar@microsoft.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@nabladev.com \
    --cc=pschneider1968@googlemail.com \
    --cc=rwarsow@gmx.de \
    --cc=shuah@kernel.org \
    --cc=sr@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

all inboxes | Powered by JetHome®