From: Steffen Maier <maier@linux.vnet.ibm.com>
To: Johannes Thumshirn <jthumshirn@suse.de>,
"Martin K . Petersen" <martin.petersen@oracle.com>
Cc: Linux Kernel Mailinglist <linux-kernel@vger.kernel.org>,
Linux SCSI Mailinglist <linux-scsi@vger.kernel.org>,
Tejun Heo <tj@kernel.org>,
Bart Van Assche <Bart.VanAssche@sandisk.com>,
Oliver Neukum <oneukum@suse.com>,
Alan Stern <stern@rowland.harvard.edu>
Subject: Re: [PATCH] scsi: use set_host_byte instead of open-coding it
Date: Wed, 11 Oct 2017 15:05:40 +0200 [thread overview]
Message-ID: <ceff38de-c8f7-9279-4769-5fcaa239ec7a@linux.vnet.ibm.com> (raw)
In-Reply-To: <20171010152939.21353-1-jthumshirn@suse.de>
On 10/10/2017 05:29 PM, Johannes Thumshirn wrote:
> Call set_host_byte() instead of open-coding it.
>
> Converted using this simple Coccinelle spatch
>
> <SmPL>
> @@
> local idexpression struct scsi_cmnd *c;
> expression E1;
> @@
>
> - c->result = E1 << 16;
> + set_host_byte(c, E1);
Maybe I misunderstand, but doesn't set_host_byte only set the host byte
but leave the other 3 parts untouched in c->result?
static inline void set_host_byte(struct scsi_cmnd *cmd, char status)
{
cmd->result = (cmd->result & 0xff00ffff) | (status << 16);
}
In contrast, assigning something to c->result resets all parts.
If so, the semantic patch would introduce a subtle semantic change.
Unless it's guaranteed that in all the touched cases, c->result always
has 0 for status, message, and driver byte before calling set_host_byte().
Bart's suggestion also sounds nice.
FYI: Originally, I only thought about using set_host_byte in that one
place fix of yours; I did not expect a full framework rework.
--
Mit freundlichen Grüßen / Kind regards
Steffen Maier
Linux on z Systems Development
IBM Deutschland Research & Development GmbH
Vorsitzende des Aufsichtsrats: Martina Koederitz
Geschaeftsfuehrung: Dirk Wittkopp
Sitz der Gesellschaft: Boeblingen
Registergericht: Amtsgericht Stuttgart, HRB 243294
next prev parent reply other threads:[~2017-10-11 13:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-10 15:29 [PATCH] scsi: use set_host_byte instead of open-coding it Johannes Thumshirn
2017-10-10 16:02 ` Bart Van Assche
2017-10-11 13:05 ` Steffen Maier [this message]
2017-10-11 13:25 ` Johannes Thumshirn
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=ceff38de-c8f7-9279-4769-5fcaa239ec7a@linux.vnet.ibm.com \
--to=maier@linux.vnet.ibm.com \
--cc=Bart.VanAssche@sandisk.com \
--cc=jthumshirn@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=oneukum@suse.com \
--cc=stern@rowland.harvard.edu \
--cc=tj@kernel.org \
/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