From: Jens Axboe <axboe@kernel.dk>
To: Chaitanya Kulkarni <kch@nvidia.com>, linux-block@vger.kernel.org
Cc: damien.lemoal@opensource.wdc.com, johannes.thumshirn@wdc.com,
ming.lei@redhat.com, bvanassche@acm.org,
shinichiro.kawasaki@wdc.com, vincent.fu@samsung.com
Subject: Re: [PATCH V2 0/9] null_blk: add modparam checks
Date: Thu, 30 Mar 2023 17:02:15 -0600 [thread overview]
Message-ID: <20f6de15-3513-c969-7095-7a93c1a4f881@kernel.dk> (raw)
In-Reply-To: <20230330213134.131298-1-kch@nvidia.com>
Please take Damien's advice from v1 and compact these patches. This is
getting somewhat out of hand and silly, imho. Are we gaming patch
counts?! If not, what's the point?
--
Jens Axboe
next prev parent reply other threads:[~2023-03-30 23:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-30 21:31 [PATCH V2 0/9] null_blk: add modparam checks Chaitanya Kulkarni
2023-03-30 21:31 ` [PATCH V2 1/9] null_blk: adjust null_param_store_val() Chaitanya Kulkarni
2023-03-30 21:31 ` [PATCH V2 2/9] null_blk: check for valid submit_queue value Chaitanya Kulkarni
2023-03-30 21:31 ` [PATCH V2 3/9] null_blk: check for valid poll_queue value Chaitanya Kulkarni
2023-03-30 21:31 ` [PATCH V2 4/9] null_blk: check for valid gb value Chaitanya Kulkarni
2023-03-30 21:31 ` [PATCH V2 5/9] null_blk: check for valid block size value Chaitanya Kulkarni
2023-03-30 22:45 ` Damien Le Moal
2023-03-30 22:52 ` Chaitanya Kulkarni
2023-03-30 22:59 ` Damien Le Moal
2023-03-30 21:31 ` [PATCH V2 6/9] null_blk: check for valid max_sectors value Chaitanya Kulkarni
2023-03-30 21:31 ` [PATCH V2 7/9] null_blk: check for valid queue depth value Chaitanya Kulkarni
2023-03-30 21:31 ` [PATCH V2 8/9] null_blk: avoid use global modparam g_queue_mode Chaitanya Kulkarni
2023-03-30 21:31 ` [PATCH V2 9/9] null_blk: avoid use global modparam g_irq_mode Chaitanya Kulkarni
2023-03-30 23:02 ` Jens Axboe [this message]
2023-03-31 4:52 ` [PATCH V2 0/9] null_blk: add modparam checks Chaitanya Kulkarni
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=20f6de15-3513-c969-7095-7a93c1a4f881@kernel.dk \
--to=axboe@kernel.dk \
--cc=bvanassche@acm.org \
--cc=damien.lemoal@opensource.wdc.com \
--cc=johannes.thumshirn@wdc.com \
--cc=kch@nvidia.com \
--cc=linux-block@vger.kernel.org \
--cc=ming.lei@redhat.com \
--cc=shinichiro.kawasaki@wdc.com \
--cc=vincent.fu@samsung.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.