[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170117141525.GA32219@lst.de>
Date: Tue, 17 Jan 2017 15:15:25 +0100
From: Christoph Hellwig <hch@....de>
To: Sreekanth Reddy <sreekanth.reddy@...adcom.com>
Cc: James Bottomley <James.Bottomley@...senpartnership.com>,
"Martin K. Petersen" <martin.petersen@...cle.com>,
David Miller <davem@...emloft.net>,
Bart Van Assche <Bart.VanAssche@...disk.com>,
Christoph Hellwig <hch@...radead.org>, jbaron@...mai.com,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
sagi@...mberg.me, Sathya Prakash <sathya.prakash@...adcom.com>,
Suganath Prabu Subramani
<suganath-prabu.subramani@...adcom.com>,
Hannes Reinecke <hare@...e.de>,
"linux-scsi@...r.kernel.org" <linux-scsi@...r.kernel.org>,
Christoph Hellwig <hch@....de>,
Chaitra Basappa <chaitra.basappa@...adcom.com>,
dledford@...hat.com
Subject: Re: [PATCH] scsi: mpt3sas: fix hang on ata passthru commands
On Tue, Jan 17, 2017 at 07:43:51PM +0530, Sreekanth Reddy wrote:
> [Sreekanth] Just for readability purpose, can use use "if (test_bit(0,
> &sas_device_priv_data->ata_command_pending)"
> instead of "if (sas_device_priv_data->ata_command_pending)".
> Since while setting & clearing the bit we are using atomic bit
> operations. I don't see any issue functionality wise.
I agree. Also while we're into nitpicking - it would be good to
give bit 0 of the bitmap a name instead of hardcoding the 0.
Except for these patch looks fine:
Reviewed-by: Christoph Hellwig <hch@....de>
Powered by blists - more mailing lists