Linux SCSI subsystem development
 help / color / mirror / Atom feed
From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: David Jeffery <djeffery@redhat.com>
Cc: "Kai Mäkisara" <Kai.Makisara@kolumbus.fi>,
	linux-scsi@vger.kernel.org,
	"Laurence Oberman" <loberman@redhat.com>
Subject: Re: [PATCH 1/2] st: separate st-unique ioctl handling from scsi common ioctl  handling
Date: Sat, 08 Nov 2025 12:22:00 -0500	[thread overview]
Message-ID: <yq1bjlcjv80.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <20251104154709.6436-1-djeffery@redhat.com> (David Jeffery's message of "Tue, 4 Nov 2025 10:46:22 -0500")


David,

> The st ioctl function currently interleaves code for handling various st
> specific ioctls with parts of code needed for handling ioctls common to
> all scsi devices. Separate out st's code for the common ioctls into a more
> manageable, separate function.

Applied to 6.19/scsi-staging, thanks!

-- 
Martin K. Petersen

  parent reply	other threads:[~2025-11-08 17:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-04 15:46 [PATCH 1/2] st: separate st-unique ioctl handling from scsi common ioctl handling David Jeffery
2025-11-04 15:46 ` [PATCH 2/2] st: skip buffer flush for information ioctls David Jeffery
2025-11-05 14:40   ` "Kai Mäkisara (Kolumbus)"
2025-11-05 17:34   ` John Meneghini
2025-11-08 17:22   ` Martin K. Petersen
2025-11-05 14:38 ` [PATCH 1/2] st: separate st-unique ioctl handling from scsi common ioctl handling "Kai Mäkisara (Kolumbus)"
2025-11-05 14:43 ` Laurence Oberman
2025-11-05 15:56 ` John Meneghini
2025-11-08 17:22 ` Martin K. Petersen [this message]
2025-11-13  2:46 ` Martin K. Petersen

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=yq1bjlcjv80.fsf@ca-mkp.ca.oracle.com \
    --to=martin.petersen@oracle.com \
    --cc=Kai.Makisara@kolumbus.fi \
    --cc=djeffery@redhat.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=loberman@redhat.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