public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: "Uwe Kleine-König" <u.kleine-koenig@baylibre.com>
Cc: Christoph Hellwig <hch@infradead.org>,
	Bart Van Assche <bvanassche@acm.org>,
	"James E.J. Bottomley" <James.Bottomley@hansenpartnership.com>,
	"Martin K. Petersen" <martin.petersen@oracle.com>,
	linux-scsi@vger.kernel.org
Subject: Re: [PATCH 2/8] scsi: Make use of bus callbacks
Date: Tue, 9 Dec 2025 23:04:40 -0800	[thread overview]
Message-ID: <aTkbiHE45DDeQhH3@infradead.org> (raw)
In-Reply-To: <77keukzmb57v2jyf26ulsystu77f2k5ta5k2vjxk5hygypzb7c@4kvu4hdty3o6>

On Wed, Dec 10, 2025 at 07:56:10AM +0100, Uwe Kleine-König wrote:
> On Tue, Dec 09, 2025 at 09:26:40PM -0800, Christoph Hellwig wrote:
> > On Tue, Dec 09, 2025 at 10:22:54PM +0100, Uwe Kleine-König wrote:
> > > I decided not to do that as part of this patch set. In case I missed a
> > > driver and for oot drivers I think it's nice and fair to not break them
> > > immediately and give its users/developers a chance to see the warning
> > > and act on it.
> > 
> > No one should care about out of tree drivers.  On the other hand
> > unfinished transitions are really annoying and have a tendency to
> > go stale.  So please go the final steps and finish it.
> 
> Given that the whole quest to remove the device_driver callbacks will go
> on for a few kernel releases and completing the transition for scsi
> yields to broken drivers without compile time issues if something is
> missed, I think it's sensible to keep them in the "working with warning"
> state for a release cycle (or even until the driver callbacks go away).

You will notice very quickly when they break.  And it's not like there's
a lot of them to start with.  Please just finish up the conversion
instead of leaving it lingering.


  reply	other threads:[~2025-12-10  7:04 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-09 20:45 [PATCH 0/8] scsi: Make use of bus callbacks Uwe Kleine-König
2025-12-09 20:45 ` [PATCH 1/8] scsi: Pass a struct scsi_driver to scsi_{,un}register_driver() Uwe Kleine-König
2025-12-10 13:14   ` Peter Wang (王信友)
2025-12-09 20:45 ` [PATCH 2/8] scsi: Make use of bus callbacks Uwe Kleine-König
2025-12-09 20:59   ` Bart Van Assche
2025-12-09 21:22     ` Uwe Kleine-König
2025-12-10  5:26       ` Christoph Hellwig
2025-12-10  6:56         ` Uwe Kleine-König
2025-12-10  7:04           ` Christoph Hellwig [this message]
2025-12-10 10:34             ` Uwe Kleine-König
2025-12-09 21:00   ` Bart Van Assche
2025-12-09 21:26     ` Uwe Kleine-König
2025-12-09 20:45 ` [PATCH 3/8] scsi: ch: Convert to scsi bus methods Uwe Kleine-König
2025-12-09 20:45 ` [PATCH 4/8] scsi: sd: " Uwe Kleine-König
2025-12-10  9:20   ` kernel test robot
2025-12-10  9:50     ` Uwe Kleine-König
2025-12-15  4:10   ` kernel test robot
2025-12-09 20:45 ` [PATCH 5/8] scsi: ses: " Uwe Kleine-König
2025-12-09 20:45 ` [PATCH 6/8] scsi: sr: " Uwe Kleine-König
2025-12-09 20:45 ` [PATCH 7/8] scsi: st: " Uwe Kleine-König
2025-12-09 20:45 ` [PATCH 8/8] scsi: ufs: " Uwe Kleine-König
2025-12-10 13:14   ` Peter Wang (王信友)

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=aTkbiHE45DDeQhH3@infradead.org \
    --to=hch@infradead.org \
    --cc=James.Bottomley@hansenpartnership.com \
    --cc=bvanassche@acm.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=u.kleine-koenig@baylibre.com \
    /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