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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Chaitanya Kulkarni <kch@xxxxxxxxxx>
Subject: Re: [PATCH 0/5] block/drivers: don't clear the flag that is not set
From: Nitesh Shetty <nj.shetty@xxxxxxxxxxx>
Date: Mon, 24 Apr 2023 14:56:41 +0530
Cc: linux-block@xxxxxxxxxxxxxxx, linux-bcache@xxxxxxxxxxxxxxx, axboe@xxxxxxxxx, josef@xxxxxxxxxxxxxx, minchan@xxxxxxxxxx, senozhatsky@xxxxxxxxxxxx, colyli@xxxxxxx, kent.overstreet@xxxxxxxxx, dlemoal@xxxxxxxxxx, johannes.thumshirn@xxxxxxx, bvanassche@xxxxxxx, vincent.fu@xxxxxxxxxxx, akinobu.mita@xxxxxxxxx, shinichiro.kawasaki@xxxxxxx, nbd@xxxxxxxxxxxxxxxx, Jason@xxxxxxxxx
Cms-type: 105P
Dlp-filter: Pass
In-reply-to: <20230424073023.38935-1-kch@nvidia.com>
User-agent: NeoMutt/20171215

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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Follow-Ups:
- Re: [PATCH 0/5] block/drivers: don't clear the flag that is not set
  - From: Chaitanya Kulkarni

References:
- [PATCH 0/5] block/drivers: don't clear the flag that is not set
  - From: Chaitanya Kulkarni

Prev by Date: [PATCH 5/5] bcache: don't clear the flag that is not set
Next by Date: Re: [PATCH 5/5] bcache: 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

[Index of Archives] [Linux ARM Kernel] [Linux Filesystem Development] [Linux ARM] [Linux Omap] [Fedora ARM] [IETF Annouce] [Security] [Bugtraq] [Linux OMAP] [Linux MIPS] [ECOS] [Asterisk Internet PBX] [Linux API]