[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <e359973d-aaf5-49e6-b1c2-89b580b7dfa8@acm.org>
Date: Mon, 22 Sep 2025 09:43:48 -0700
From: Bart Van Assche <bvanassche@....org>
To: Xinhui Yang <cyan@...no.uk>, linux-scsi@...r.kernel.org
Cc: stable@...r.kernel.org, Mingcong Bai <jeffbai@...c.io>,
Kexy Biscuit <kexybiscuit@...c.io>, Oliver Neukum <oliver@...kum.org>,
Ali Akcaagac <aliakc@....de>, Jamie Lenehan <lenehan@...bble.org>,
"James E.J. Bottomley" <James.Bottomley@...senPartnership.com>,
"Martin K. Petersen" <martin.petersen@...cle.com>,
open list <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2] scsi: dc395x: correctly discard the return value in
certain reads
On 9/22/25 8:26 AM, Xinhui Yang wrote:
> -#define DC395x_LOCK_IO(dev,flags) spin_lock_irqsave(((struct Scsi_Host *)dev)->host_lock, flags)
> -#define DC395x_UNLOCK_IO(dev,flags) spin_unlock_irqrestore(((struct Scsi_Host *)dev)->host_lock, flags)
> +#define DC395x_LOCK_IO(dev, flags) spin_lock_irqsave(((struct Scsi_Host *)dev)->host_lock, flags)
> +#define DC395x_UNLOCK_IO(dev, flags) spin_unlock_irqrestore(((struct Scsi_Host *)dev)->host_lock, flags)
Are these whitespace-only changes? Such changes shouldn't be included in
a Cc: stable patch.
Thanks,
Bart.
Powered by blists - more mailing lists