From: sashiko-bot@kernel.org
To: "Randy Dunlap" <rdunlap@infradead.org>
Cc: "Jonathan Corbet" <corbet@lwn.net>,
"Shuah Khan" <skhan@linuxfoundation.org>,
"David Hildenbrand" <david@kernel.org>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Jason Gunthorpe" <jgg@nvidia.com>,
"Leon Romanovsky" <leonro@nvidia.com>,
linux-mm@kvack.org, "Jaroslav Kysela" <perex@perex.cz>,
"Takashi Iwai" <tiwai@suse.com>,
linux-sound@vger.kernel.org, "Jens Axboe" <axboe@kernel.dk>,
"Marcel Holtmann" <marcel@holtmann.org>,
"Luiz Augusto von Dentz" <luiz.dentz@gmail.com>,
"Willem de Bruijn" <willemdebruijn.kernel@gmail.com>,
"Jason Wang" <jasowangio@gmail.com>,
"David Heidelberg" <david@ixit.cz>,
"Chas Williams" <3chas3@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
"Eric Dumazet" <edumazet@kernel.org>,
"Jakub Kicinski" <kuba@kernel.org>,
"Paolo Abeni" <pabeni@redhat.com>, "Helge Deller" <deller@gmx.de>,
dri-devel@lists.freedesktop.org,
MPT-FusionLinux.pdl@broadcom.com,
"James E.J. Bottomley" <James.Bottomley@HansenPartnership.com>,
"Martin K. Petersen" <mkp@kernel.org>,
linux-scsi@vger.kernel.org,
"Miquel Raynal" <miquel.raynal@bootlin.com>,
"Richard Weinberger" <richard@nod.at>,
"Vignesh Raghavendra" <vigneshr@ti.com>,
"Zhihao Cheng" <chengzhihao1@huawei.com>,
linux-mtd@lists.infradead.org,
"Neill Kapron" <nkapron@google.com>,
"Andrey Konovalov" <andreyknvl@gmail.com>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
linux-usb@vger.kernel.org, "Juergen Gross" <jgross@suse.com>,
"Stefano Stabellini" <sstabellini@kernel.org>,
"Hans de Goede" <hansg@kernel.org>,
"Arnd Bergmann" <arnd@arndb.de>,
"Michael S. Tsirkin" <mst@redhat.com>,
"Eugenio Pérez" <eperezma@redhat.com>,
"Sean Christopherson" <seanjc@google.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
kvm@vger.kernel.org, virtualization@lists.linux.dev,
"Jan Kara" <jack@suse.cz>, "Theodore Ts'o" <tytso@mit.edu>,
linux-ext4@vger.kernel.org, "Mike Marshall" <hubcap@omnibond.com>,
devel@lists.orangefs.org, "Paulo Alcantara" <pc@manguebit.org>,
"Namjae Jeon" <linkinjeon@kernel.org>,
"Jaegeuk Kim" <jaegeuk@kernel.org>, "Chao Yu" <chao@kernel.org>,
"Florian Fainelli" <florian.fainelli@broadcom.com>,
"Broadcom internal kernel review list"
<bcm-kernel-feedback-list@broadcom.com>,
"Tzung-Bi Shih" <tzungbi@kernel.org>,
"Benson Leung" <bleung@chromium.org>,
"David Airlie" <airlied@gmail.com>,
"Simona Vetter" <simona@ffwll.ch>,
"Alex Deucher" <alexander.deucher@amd.com>,
"Christian König" <christian.koenig@amd.com>,
amd-gfx@lists.freedesktop.org,
"Jani Nikula" <jani.nikula@linux.intel.com>,
"Joonas Lahtinen" <joonas.lahtinen@linux.intel.com>,
"Rodrigo Vivi" <rodrigo.vivi@intel.com>,
"Tvrtko Ursulin" <tursulin@ursulin.net>,
intel-gfx@lists.freedesktop.org,
"Matthew Brost" <matthew.brost@intel.com>,
"Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
intel-xe@lists.freedesktop.org
Subject: Re: [PATCH 02/12] docs: ioctl-number: update sound entries
Date: Sun, 15 Nov 2026 20:27:39 +0000 [thread overview]
Message-ID: <sashiko-outbox-215802@kernel.org> (raw)
In-Reply-To: <20261114202653.3113381-3-rdunlap@infradead.org>
Thank you for your contribution! Sashiko AI review found 5 potential
issues to consider:
- [Low] docs: ioctl-number: wrong code, range, and conflict marker for
scarlett2.h
- [Low] docs: ioctl-number: incomplete sequence range for sound/pcm.h
- [Low] docs: ioctl-number: incomplete range and tab char for
sound/core/pcm_compat.c
- [Low] docs: ioctl-number: incomplete sequence range for
sound/core/seq/seq_compat.c
- [Low] docs: ioctl-number: missing conflict! marker on switchtec.c
under code 'W'
--
commit 0316dc2cd0f479a35471758d208f4335b8fbc617
Author: Randy Dunlap <rdunlap@infradead.org>
docs: ioctl-number: update sound entries
This commit updates the ioctl-number documentation table with additional
sound header and compat files and adjusts sequence number ranges for sound
ioctls.
> diff --git a/Documentation/userspace-api/ioctl/ioctl-number.rst b/Documentation/userspace-api/ioctl/ioctl-number.rst
> index e1d56d5cccd14..dac65f59d05e2 100644
> --- a/Documentation/userspace-api/ioctl/ioctl-number.rst
> +++ b/Documentation/userspace-api/ioctl/ioctl-number.rst
> @@ -122,11 +122,14 @@ Code Seq# Include File Comments
> 'A' 00-0F linux/agpgart.h, conflict!
> drivers/char/agp/compat_ioctl.h
> 'A' 00-7F sound/asound.h conflict!
> +'A' 20 sound/pcm.h conflict!
[Severity: Low]
Should the sequence range for sound/pcm.h be 20-24 instead of 20? In
include/sound/pcm.h, SNDRV_PCM_IOCTL_STATUS_EXT64 and
SNDRV_PCM_IOCTL_STATUS_EXT32 also define ioctls using _IOWR('A', 0x24, ...).
> +'A' 20-53 sound/core/pcm_compat.c conflict!
[Severity: Low]
Should the sequence range for sound/core/pcm_compat.c start at 10 rather
than 20? The compat ioctl enum in sound/core/pcm_compat.c starts with
SNDRV_PCM_IOCTL_HW_REFINE32 (_IOWR('A', 0x10, ...)),
SNDRV_PCM_IOCTL_HW_PARAMS32 (0x11), and SNDRV_PCM_IOCTL_SW_PARAMS32 (0x13).
Also, there is a literal tab character right after sound/core/pcm_compat.c
instead of spaces.
[ ... ]
> @@ -160,7 +164,9 @@ Code Seq# Include File Comments
> 'H' 10-1F sound/hda_hwdep.h conflict!
> 'H' 40-4F sound/hdspm.h conflict!
> 'H' 40-4F sound/hdsp.h conflict!
> +'H' 60-63 sound/scarlett2.h
[Severity: Low]
Should sound/scarlett2.h be listed under code 'S' with range 60-64 and a
conflict! marker instead of 'H' 60-63? In include/uapi/sound/scarlett2.h,
all ioctls use code 'S' from SCARLETT2_IOCTL_PVERSION (_IOR('S', 0x60, int))
through SCARLETT2_IOCTL_GET_ERASE_PROGRESS (_IOR('S', 0x64, ...)), which
overlaps with linux/cdrom.h, sound/asequencer.h, and sound/fcp.h.
[ ... ]
> @@ -204,6 +210,8 @@ Code Seq# Include File Comments
> 'S' 80-81 scsi/scsi_ioctl.h conflict!
> 'S' 82-FF scsi/scsi.h conflict!
> 'S' 00-7F sound/asequencer.h conflict!
> +'S' 21-23 sound/core/seq/seq_compat.c conflict!
[Severity: Low]
Should the sequence range for sound/core/seq/seq_compat.c be 20-52 instead
of 21-23? That file also defines SNDRV_SEQ_IOCTL_CREATE_PORT32
(_IOWR('S', 0x20, ...)) and SNDRV_SEQ_IOCTL_QUERY_NEXT_PORT32
(_IOWR('S', 0x52, ...)).
[ ... ]
> @@ -219,7 +227,7 @@ Code Seq# Include File Comments
> 'V' C0 media/si4713.h conflict!
> 'W' 00-1F linux/watchdog.h conflict!
> 'W' 00-1F linux/wanrouter.h conflict! (pre 3.9)
> -'W' 00-3F sound/asound.h conflict!
> +'W' 00-41 sound/asound.h conflict!
> 'W' 40-5F drivers/pci/switch/switchtec.c
[Severity: Low]
Does the drivers/pci/switch/switchtec.c entry now need a conflict! marker
as well, since extending sound/asound.h to 00-41 causes the two ranges to
overlap on 40-41?
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261114202653.3113381-1-rdunlap@infradead.org?part=2
WARNING: multiple messages have this Message-ID (diff)
From: sashiko-bot@kernel.org
To: "Randy Dunlap" <rdunlap@infradead.org>
Cc: "Jonathan Corbet" <corbet@lwn.net>,
"Shuah Khan" <skhan@linuxfoundation.org>,
"David Hildenbrand" <david@kernel.org>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Jason Gunthorpe" <jgg@nvidia.com>,
"Leon Romanovsky" <leonro@nvidia.com>,
linux-mm@kvack.org, "Jaroslav Kysela" <perex@perex.cz>,
"Takashi Iwai" <tiwai@suse.com>,
linux-sound@vger.kernel.org, "Jens Axboe" <axboe@kernel.dk>,
"Marcel Holtmann" <marcel@holtmann.org>,
"Luiz Augusto von Dentz" <luiz.dentz@gmail.com>,
"Willem de Bruijn" <willemdebruijn.kernel@gmail.com>,
"Jason Wang" <jasowangio@gmail.com>,
"David Heidelberg" <david@ixit.cz>,
"Chas Williams" <3chas3@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
"Eric Dumazet" <edumazet@kernel.org>,
"Jakub Kicinski" <kuba@kernel.org>,
"Paolo Abeni" <pabeni@redhat.com>, "Helge Deller" <deller@gmx.de>,
dri-devel@lists.freedesktop.org,
MPT-FusionLinux.pdl@broadcom.com,
"James E.J. Bottomley" <James.Bottomley@HansenPartnership.com>,
"Martin K. Petersen" <mkp@kernel.org>,
linux-scsi@vger.kernel.org,
"Miquel Raynal" <miquel.raynal@bootlin.com>,
"Richard Weinberger" <richard@nod.at>,
"Vignesh Raghavendra" <vigneshr@ti.com>,
"Zhihao Cheng" <chengzhihao1@huawei.com>,
linux-mtd@lists.infradead.org,
"Neill Kapron" <nkapron@google.com>,
"Andrey Konovalov" <andreyknvl@gmail.com>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
linux-usb@vger.kernel.org, "Juergen Gross" <jgross@suse.com>,
"Stefano Stabellini" <sstabellini@kernel.org>,
"Hans de Goede" <hansg@kernel.org>,
"Arnd Bergmann" <arnd@arndb.de>,
"Michael S. Tsirkin" <mst@redhat.com>,
"Eugenio Pérez" <eperezma@redhat.com>,
"Sean Christopherson" <seanjc@google.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
kvm@vger.kernel.org, virtualization@lists.linux.dev,
"Jan Kara" <jack@suse.cz>, "Theodore Ts'o" <tytso@mit.edu>,
linux-ext4@vger.kernel.org, "Mike Marshall" <hubcap@omnibond.com>,
devel@lists.orangefs.org, "Paulo Alcantara" <pc@manguebit.org>,
"Namjae Jeon" <linkinjeon@kernel.org>,
"Jaegeuk Kim" <jaegeuk@kernel.org>, "Chao Yu" <chao@kernel.org>,
"Florian Fainelli" <florian.fainelli@broadcom.com>,
"Broadcom internal kernel review list"
<bcm-kernel-feedback-list@broadcom.com>,
"Tzung-Bi Shih" <tzungbi@kernel.org>,
"Benson Leung" <bleung@chromium.org>,
"David Airlie" <airlied@gmail.com>,
"Simona Vetter" <simona@ffwll.ch>,
"Alex Deucher" <alexander.deucher@amd.com>,
"Christian König" <christian.koenig@amd.com>,
amd-gfx@lists.freedesktop.org,
"Jani Nikula" <jani.nikula@linux.intel.com>,
"Joonas Lahtinen" <joonas.lahtinen@linux.intel.com>,
"Rodrigo Vivi" <rodrigo.vivi@intel.com>,
"Tvrtko Ursulin" <tursulin@ursulin.net>,
intel-gfx@lists.freedesktop.org,
"Matthew Brost" <matthew.brost@intel.com>,
"Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
intel-xe@lists.freedesktop.org
Subject: Re: [PATCH 02/12] docs: ioctl-number: update sound entries
Date: Sun, 15 Nov 2026 20:27:39 +0000 [thread overview]
Message-ID: <sashiko-outbox-215802@kernel.org> (raw)
In-Reply-To: <20261114202653.3113381-3-rdunlap@infradead.org>
Thank you for your contribution! Sashiko AI review found 5 potential
issues to consider:
- [Low] docs: ioctl-number: wrong code, range, and conflict marker for
scarlett2.h
- [Low] docs: ioctl-number: incomplete sequence range for sound/pcm.h
- [Low] docs: ioctl-number: incomplete range and tab char for
sound/core/pcm_compat.c
- [Low] docs: ioctl-number: incomplete sequence range for
sound/core/seq/seq_compat.c
- [Low] docs: ioctl-number: missing conflict! marker on switchtec.c
under code 'W'
--
commit 0316dc2cd0f479a35471758d208f4335b8fbc617
Author: Randy Dunlap <rdunlap@infradead.org>
docs: ioctl-number: update sound entries
This commit updates the ioctl-number documentation table with additional
sound header and compat files and adjusts sequence number ranges for sound
ioctls.
> diff --git a/Documentation/userspace-api/ioctl/ioctl-number.rst b/Documentation/userspace-api/ioctl/ioctl-number.rst
> index e1d56d5cccd14..dac65f59d05e2 100644
> --- a/Documentation/userspace-api/ioctl/ioctl-number.rst
> +++ b/Documentation/userspace-api/ioctl/ioctl-number.rst
> @@ -122,11 +122,14 @@ Code Seq# Include File Comments
> 'A' 00-0F linux/agpgart.h, conflict!
> drivers/char/agp/compat_ioctl.h
> 'A' 00-7F sound/asound.h conflict!
> +'A' 20 sound/pcm.h conflict!
[Severity: Low]
Should the sequence range for sound/pcm.h be 20-24 instead of 20? In
include/sound/pcm.h, SNDRV_PCM_IOCTL_STATUS_EXT64 and
SNDRV_PCM_IOCTL_STATUS_EXT32 also define ioctls using _IOWR('A', 0x24, ...).
> +'A' 20-53 sound/core/pcm_compat.c conflict!
[Severity: Low]
Should the sequence range for sound/core/pcm_compat.c start at 10 rather
than 20? The compat ioctl enum in sound/core/pcm_compat.c starts with
SNDRV_PCM_IOCTL_HW_REFINE32 (_IOWR('A', 0x10, ...)),
SNDRV_PCM_IOCTL_HW_PARAMS32 (0x11), and SNDRV_PCM_IOCTL_SW_PARAMS32 (0x13).
Also, there is a literal tab character right after sound/core/pcm_compat.c
instead of spaces.
[ ... ]
> @@ -160,7 +164,9 @@ Code Seq# Include File Comments
> 'H' 10-1F sound/hda_hwdep.h conflict!
> 'H' 40-4F sound/hdspm.h conflict!
> 'H' 40-4F sound/hdsp.h conflict!
> +'H' 60-63 sound/scarlett2.h
[Severity: Low]
Should sound/scarlett2.h be listed under code 'S' with range 60-64 and a
conflict! marker instead of 'H' 60-63? In include/uapi/sound/scarlett2.h,
all ioctls use code 'S' from SCARLETT2_IOCTL_PVERSION (_IOR('S', 0x60, int))
through SCARLETT2_IOCTL_GET_ERASE_PROGRESS (_IOR('S', 0x64, ...)), which
overlaps with linux/cdrom.h, sound/asequencer.h, and sound/fcp.h.
[ ... ]
> @@ -204,6 +210,8 @@ Code Seq# Include File Comments
> 'S' 80-81 scsi/scsi_ioctl.h conflict!
> 'S' 82-FF scsi/scsi.h conflict!
> 'S' 00-7F sound/asequencer.h conflict!
> +'S' 21-23 sound/core/seq/seq_compat.c conflict!
[Severity: Low]
Should the sequence range for sound/core/seq/seq_compat.c be 20-52 instead
of 21-23? That file also defines SNDRV_SEQ_IOCTL_CREATE_PORT32
(_IOWR('S', 0x20, ...)) and SNDRV_SEQ_IOCTL_QUERY_NEXT_PORT32
(_IOWR('S', 0x52, ...)).
[ ... ]
> @@ -219,7 +227,7 @@ Code Seq# Include File Comments
> 'V' C0 media/si4713.h conflict!
> 'W' 00-1F linux/watchdog.h conflict!
> 'W' 00-1F linux/wanrouter.h conflict! (pre 3.9)
> -'W' 00-3F sound/asound.h conflict!
> +'W' 00-41 sound/asound.h conflict!
> 'W' 40-5F drivers/pci/switch/switchtec.c
[Severity: Low]
Does the drivers/pci/switch/switchtec.c entry now need a conflict! marker
as well, since extending sound/asound.h to 00-41 causes the two ranges to
overlap on 40-41?
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261114202653.3113381-1-rdunlap@infradead.org?part=2
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent 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 ` [f2fs-dev] " Randy Dunlap
2026-11-14 20:26 ` Randy Dunlap
2026-11-14 20:26 ` [PATCH 01/12] docs: ioctl-number: update MM entries Randy Dunlap
2026-11-14 20:26 ` [f2fs-dev] " Randy Dunlap
2026-11-14 20:26 ` 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 ` [f2fs-dev] " David Hildenbrand (Arm) via Linux-f2fs-devel
2026-11-15 16:58 ` David Hildenbrand (Arm)
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 ` [f2fs-dev] " Randy Dunlap
2026-11-14 20:26 ` 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 [this message]
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 ` [f2fs-dev] " Randy Dunlap
2026-11-14 20:26 ` 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 ` [f2fs-dev] " Randy Dunlap
2026-11-14 20:26 ` 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 ` [f2fs-dev] " Randy Dunlap
2026-11-14 20:26 ` 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 ` [f2fs-dev] " Randy Dunlap
2026-11-14 20:26 ` Randy Dunlap
2026-11-15 20:27 ` sashiko-bot
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 ` [f2fs-dev] " Randy Dunlap
2026-11-14 20:26 ` 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 ` [f2fs-dev] " Randy Dunlap
2026-11-14 20:26 ` 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 ` [f2fs-dev] " Randy Dunlap
2026-11-14 20:26 ` 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 ` [f2fs-dev] " Randy Dunlap
2026-11-14 20:26 ` 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-215802@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=3chas3@gmail.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=MPT-FusionLinux.pdl@broadcom.com \
--cc=airlied@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=andreyknvl@gmail.com \
--cc=arnd@arndb.de \
--cc=axboe@kernel.dk \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=bleung@chromium.org \
--cc=chao@kernel.org \
--cc=chengzhihao1@huawei.com \
--cc=christian.koenig@amd.com \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=david@ixit.cz \
--cc=david@kernel.org \
--cc=deller@gmx.de \
--cc=devel@lists.orangefs.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=edumazet@kernel.org \
--cc=eperezma@redhat.com \
--cc=florian.fainelli@broadcom.com \
--cc=gregkh@linuxfoundation.org \
--cc=hansg@kernel.org \
--cc=hubcap@omnibond.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jack@suse.cz \
--cc=jaegeuk@kernel.org \
--cc=jani.nikula@linux.intel.com \
--cc=jasowangio@gmail.com \
--cc=jgg@nvidia.com \
--cc=jgross@suse.com \
--cc=joonas.lahtinen@linux.intel.com \
--cc=kuba@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=leonro@nvidia.com \
--cc=linkinjeon@kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=matthew.brost@intel.com \
--cc=miquel.raynal@bootlin.com \
--cc=mkp@kernel.org \
--cc=mst@redhat.com \
--cc=nkapron@google.com \
--cc=pabeni@redhat.com \
--cc=pbonzini@redhat.com \
--cc=pc@manguebit.org \
--cc=perex@perex.cz \
--cc=rdunlap@infradead.org \
--cc=richard@nod.at \
--cc=rodrigo.vivi@intel.com \
--cc=sashiko-reviews@lists.linux.dev \
--cc=seanjc@google.com \
--cc=simona@ffwll.ch \
--cc=skhan@linuxfoundation.org \
--cc=sstabellini@kernel.org \
--cc=thomas.hellstrom@linux.intel.com \
--cc=tiwai@suse.com \
--cc=tursulin@ursulin.net \
--cc=tytso@mit.edu \
--cc=tzungbi@kernel.org \
--cc=vigneshr@ti.com \
--cc=virtualization@lists.linux.dev \
--cc=willemdebruijn.kernel@gmail.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 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.