[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <8c91e5a4-4f01-4906-a002-4a9032cb8da3@oracle.com>
Date: Thu, 12 Sep 2024 15:58:37 +0100
From: John Garry <john.g.garry@...cle.com>
To: Christoph Hellwig <hch@....de>
Cc: axboe@...nel.dk, song@...nel.org, yukuai3@...wei.com, kbusch@...nel.org,
sagi@...mberg.me, James.Bottomley@...senPartnership.com,
martin.petersen@...cle.com, linux-block@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-raid@...r.kernel.org,
linux-nvme@...ts.infradead.org, linux-scsi@...r.kernel.org
Subject: Re: [PATCH RFC 2/4] block: Add BLK_FEAT_ATOMIC_WRITES flag
On 12/09/2024 14:16, Christoph Hellwig wrote:
>> @@ -176,7 +176,7 @@ static void blk_validate_atomic_write_limits(struct queue_limits *lim)
>> {
>> unsigned int boundary_sectors;
>>
>> - if (!lim->atomic_write_hw_max)
>> + if (!(lim->features & BLK_FEAT_ATOMIC_WRITES) || !lim->atomic_write_hw_max)
> Overly long line here.
ok
>
> Otherwise this looks good:
>
> Reviewed-by: Christoph Hellwig<hch@....de>
cheers
Powered by blists - more mailing lists