All of lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Randy Dunlap" <rdunlap@infradead.org>
Cc: linux-usb@vger.kernel.org, virtualization@lists.linux.dev,
	linux-ext4@vger.kernel.org, tytso@mit.edu,
	"Michael S. Tsirkin" <mst@redhat.com>,
	"Eugenio Perez" <eperezma@redhat.com>
Subject: Re: [PATCH 06/12] docs: ioctl-number: update SCSI entries
Date: Sun, 15 Nov 2026 20:27:48 +0000	[thread overview]
Message-ID: <sashiko-outbox-215806@kernel.org> (raw)
In-Reply-To: <20261114202653.3113381-7-rdunlap@infradead.org>

> Update the list of files where SCSI ioctls are defined and update the
> ranges of function numbers that are used.
> 
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>

Sashiko has reviewed this patch and found no issues.

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261114202653.3113381-1-rdunlap@infradead.org?part=6


  reply	other threads:[~2026-11-15 20:27 UTC|newest]

Thread overview: 84+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-14 20:26 [PATCH 00/12] docs: ioctl-number: update entries Randy Dunlap
2026-11-14 20:26 ` Randy Dunlap
2026-11-14 20:26 ` [f2fs-dev] " Randy Dunlap
2026-11-14 20:26 ` [PATCH 01/12] docs: ioctl-number: update MM entries Randy Dunlap
2026-11-14 20:26   ` Randy Dunlap
2026-11-14 20:26   ` [f2fs-dev] " Randy Dunlap
2026-11-15  0:43   ` docs: ioctl-number: update entries bluez.test.bot
2026-11-15 16:58   ` [PATCH 01/12] docs: ioctl-number: update MM entries David Hildenbrand (Arm)
2026-11-15 16:58     ` David Hildenbrand (Arm)
2026-11-15 16:58     ` [f2fs-dev] " David Hildenbrand (Arm) via Linux-f2fs-devel
2026-11-16  0:45     ` Randy Dunlap
2026-11-16  0:45       ` [f2fs-dev] " Randy Dunlap
2026-11-16  0:45       ` Randy Dunlap
2026-11-15 20:27   ` sashiko-bot
2026-11-14 20:26 ` [PATCH 02/12] docs: ioctl-number: update sound entries Randy Dunlap
2026-11-14 20:26   ` Randy Dunlap
2026-11-14 20:26   ` [f2fs-dev] " Randy Dunlap
2026-11-15  1:19   ` Takashi Sakamoto
2026-11-15  1:19     ` Takashi Sakamoto
2026-11-15  1:19     ` [f2fs-dev] " Takashi Sakamoto
2026-11-15 20:27   ` sashiko-bot
2026-11-15 20:27     ` sashiko-bot
2026-11-18  0:37     ` Randy Dunlap
2026-11-18  0:37       ` Randy Dunlap
2026-11-14 20:26 ` [PATCH 03/12] docs: ioctl-number: update block entries Randy Dunlap
2026-11-14 20:26   ` Randy Dunlap
2026-11-14 20:26   ` [f2fs-dev] " Randy Dunlap
2026-11-15 20:27   ` sashiko-bot
2026-11-14 20:26 ` [PATCH 04/12] docs: ioctl-number: update networking entries Randy Dunlap
2026-11-14 20:26   ` Randy Dunlap
2026-11-14 20:26   ` [f2fs-dev] " Randy Dunlap
2026-11-15 20:27   ` sashiko-bot
2026-11-15 20:27     ` sashiko-bot
2026-11-18  0:42     ` Randy Dunlap
2026-11-18  0:42       ` Randy Dunlap
2026-11-14 20:26 ` [PATCH 05/12] docs: ioctl-number: update video/fbdev entries Randy Dunlap
2026-11-14 20:26   ` Randy Dunlap
2026-11-14 20:26   ` [f2fs-dev] " Randy Dunlap
2026-11-15 20:27   ` sashiko-bot
2026-11-14 20:26 ` [PATCH 06/12] docs: ioctl-number: update SCSI entries Randy Dunlap
2026-11-14 20:26   ` Randy Dunlap
2026-11-14 20:26   ` [f2fs-dev] " Randy Dunlap
2026-11-15 20:27   ` sashiko-bot [this message]
2026-11-14 20:26 ` [PATCH 07/12] docs: ioctl-number: update MTD entries Randy Dunlap
2026-11-14 20:26   ` Randy Dunlap
2026-11-14 20:26   ` [f2fs-dev] " Randy Dunlap
2026-11-15 20:27   ` sashiko-bot
2026-11-15 20:27     ` sashiko-bot
2026-11-18  0:45     ` Randy Dunlap
2026-11-18  0:45       ` Randy Dunlap
2026-11-14 20:26 ` [PATCH 08/12] docs: ioctl-number: update USB entries Randy Dunlap
2026-11-14 20:26   ` Randy Dunlap
2026-11-14 20:26   ` [f2fs-dev] " Randy Dunlap
2026-11-15 20:27   ` sashiko-bot
2026-11-14 20:26 ` [PATCH 09/12] docs: ioctl-number: update virtualization entries Randy Dunlap
2026-11-14 20:26   ` Randy Dunlap
2026-11-14 20:26   ` [f2fs-dev] " Randy Dunlap
2026-11-15 20:27   ` sashiko-bot
2026-11-16 14:26   ` Sean Christopherson
2026-11-16 14:26     ` [f2fs-dev] " Sean Christopherson via Linux-f2fs-devel
2026-11-16 14:26     ` Sean Christopherson
2026-11-16 22:21     ` Randy Dunlap
2026-11-16 22:21       ` [f2fs-dev] " Randy Dunlap
2026-11-16 22:21       ` Randy Dunlap
2026-11-14 20:26 ` [PATCH 10/12] docs: ioctl-number: update FS entries Randy Dunlap
2026-11-14 20:26   ` Randy Dunlap
2026-11-14 20:26   ` [f2fs-dev] " Randy Dunlap
2026-11-15 20:27   ` sashiko-bot
2026-11-15 20:27     ` sashiko-bot
2026-11-18  0:49     ` Randy Dunlap
2026-11-18  0:49       ` Randy Dunlap
2026-11-14 20:26 ` [PATCH 11/12] docs: ioctl-number: update platform entries Randy Dunlap
2026-11-14 20:26   ` Randy Dunlap
2026-11-14 20:26   ` [f2fs-dev] " Randy Dunlap
2026-11-15 20:28   ` sashiko-bot
2026-11-14 20:26 ` [PATCH 12/12] docs: ioctl-number: update DRM entries Randy Dunlap
2026-11-14 20:26   ` Randy Dunlap
2026-11-14 20:26   ` [f2fs-dev] " Randy Dunlap
2026-11-15 20:28   ` sashiko-bot
2026-11-14 20:38 ` ✓ CI.KUnit: success for docs: ioctl-number: update entries Patchwork
2026-11-14 21:14 ` ✓ Xe.CI.BAT: " Patchwork
2026-11-14 21:24 ` ✓ i915.CI.BAT: " Patchwork
2026-11-14 22:28 ` ✗ Xe.CI.FULL: failure " Patchwork
2026-11-15  6:16 ` ✗ i915.CI.Full: " Patchwork

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=sashiko-outbox-215806@kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=eperezma@redhat.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=mst@redhat.com \
    --cc=rdunlap@infradead.org \
    --cc=sashiko-reviews@lists.linux.dev \
    --cc=tytso@mit.edu \
    --cc=virtualization@lists.linux.dev \
    /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.