Re: [PATCH 0/5] block/drivers: don't clear the flag that is not set

To: Chaitanya Kulkarni <kch@nvidia.com>
Cc: linux-block@vger.kernel.org, linux-bcache@vger.kernel.org, axboe@kernel.dk, josef@toxicpanda.com, minchan@kernel.org, senozhatsky@chromium.org, colyli@suse.de, kent.overstreet@gmail.com, dlemoal@kernel.org, johannes.thumshirn@wdc.com, bvanassche@acm.org, vincent.fu@samsung.com, akinobu.mita@gmail.com, shinichiro.kawasaki@wdc.com, nbd@other.debian.org, Jason@zx2c4.com
Subject: Re: [PATCH 0/5] block/drivers: don't clear the flag that is not set
From: Nitesh Shetty <nj.shetty@samsung.com>
Date: Mon, 24 Apr 2023 14:56:41 +0530
Message-id: <[🔎] 20230424092641.u6u25eyojewvasj4@green245>
In-reply-to: <20230424073023.38935-1-kch@nvidia.com>
References: <20230424073023.38935-1-kch@nvidia.com> <CGME20230424092940epcas5p3407002e7d5c79593ffbafc38f2b49e51@epcas5p3.samsung.com>

On 23/04/24 12:30AM, Chaitanya Kulkarni wrote:

null_blk
brd
nbd
zram
bcache


Any particular reason for leaving out mtip and s390 drivers ?

Will it be better to use the flag similar to scsi devices and
use it for random number generation ?

Otherwise looks good to me.

Regards,
Nitesh Shetty

Reply to:

Follow-Ups:
- Re: [PATCH 0/5] block/drivers: don't clear the flag that is not set
  - From: Chaitanya Kulkarni <chaitanyak@nvidia.com>

Prev by Date: [PATCH 5/5] bcache: don't clear the flag that is not set
Next by Date: [PATCH 2/5] brd: don't clear the flag that is not set
Previous by thread: Re: [PATCH 5/5] bcache: don't clear the flag that is not set
Next by thread: Re: [PATCH 0/5] block/drivers: don't clear the flag that is not set
Index(es):
- Date
- Thread