public inbox for linux-raid@vger.kernel.org
 help / color / mirror / Atom feed
From: Chaitanya Kulkarni <kch@nvidia.com>
To: <linan122@huawei.com>, <song@kernel.org>, <yukuai@fnnas.com>,
	<hch@lst.de>, <sagi@grimberg.me>, <axboe@kernel.dk>
Cc: <linux-raid@vger.kernel.org>, <linux-nvme@lists.infradead.org>,
	<linux-block@vger.kernel.org>,
	Chaitanya Kulkarni <kch@nvidia.com>
Subject: [PATCH V4 0/3] block: ignore discard return value
Date: Wed, 11 Feb 2026 12:44:35 -0800	[thread overview]
Message-ID: <20260211204438.22568-1-kch@nvidia.com> (raw)

Hi,

This version has remaining patches from the original series to change
__blkdev_issue_discard() return type from int to void.

First two patches make md and nvmet drivers ignore the return value of
__blkdev_issue_discard() call and last patch changes the actual function
return type from int to void.

-ck

V3->V4:-

* Rebase md and nvmet patch on latest linux-block/for-next
* Add a last patch to change the return type of
  __blkdev_issue_discard() from int to void now that all call sites
  are fixed.

Chaitanya Kulkarni (3):
  md: ignore discard return value
  nvmet: ignore discard return value
  block: change return type to void

 block/blk-lib.c                   |  3 +--
 drivers/md/md.c                   |  4 ++--
 drivers/nvme/target/io-cmd-bdev.c | 28 +++++++---------------------
 include/linux/blkdev.h            |  2 +-
 4 files changed, 11 insertions(+), 26 deletions(-)

-- 
2.39.5


             reply	other threads:[~2026-02-11 20:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-11 20:44 Chaitanya Kulkarni [this message]
2026-02-11 20:44 ` [PATCH V4 1/3] md: ignore discard return value Chaitanya Kulkarni
2026-02-11 20:44 ` [PATCH V4 2/3] nvmet: " Chaitanya Kulkarni
2026-02-11 20:44 ` [PATCH V4 3/3] block: change return type to void Chaitanya Kulkarni
2026-02-12 10:15 ` [PATCH V4 0/3] block: ignore discard return value Christoph Hellwig
2026-02-12 11:27 ` Jens Axboe

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=20260211204438.22568-1-kch@nvidia.com \
    --to=kch@nvidia.com \
    --cc=axboe@kernel.dk \
    --cc=hch@lst.de \
    --cc=linan122@huawei.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=sagi@grimberg.me \
    --cc=song@kernel.org \
    --cc=yukuai@fnnas.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox