All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+f2fs@kernel.org
To: Chaitanya Kulkarni <ckulkarnilinux@gmail.com>
Cc: axboe@kernel.dk, agk@redhat.com, snitzer@kernel.org,
	mpatocka@redhat.com, song@kernel.org, yukuai@fnnas.com,
	hch@lst.de, sagi@grimberg.me, kch@nvidia.com, jaegeuk@kernel.org,
	chao@kernel.org, cem@kernel.org, dm-devel@lists.linux.dev,
	linux-raid@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-nvme@lists.infradead.org,
	linux-f2fs-devel@lists.sourceforge.net,
	linux-block@vger.kernel.org, bpf@vger.kernel.org,
	linux-xfs@vger.kernel.org
Subject: Re: [f2fs-dev] [PATCH V3 0/6] block: ignore __blkdev_issue_discard() ret value
Date: Tue, 09 Dec 2025 17:18:47 +0000	[thread overview]
Message-ID: <176530072781.4018985.3920629164173659180.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251124234806.75216-1-ckulkarnilinux@gmail.com>

Hello:

This series was applied to jaegeuk/f2fs.git (dev)
by Jens Axboe <axboe@kernel.dk>:

On Mon, 24 Nov 2025 15:48:00 -0800 you wrote:
> Hi,
> 
> __blkdev_issue_discard() only returns value 0, that makes post call
> error checking code dead. This patch series revmoes this dead code at
> all the call sites and adjust the callers.
> 
> Please note that it doesn't change the return type of the function from
> int to void in this series, it will be done once this series gets merged
> smoothly.
> 
> [...]

Here is the summary with links:
  - [f2fs-dev,V3,1/6] block: ignore discard return value
    https://git.kernel.org/jaegeuk/f2fs/c/7d09a8e25121
  - [f2fs-dev,V3,2/6] md: ignore discard return value
    (no matching commit)
  - [f2fs-dev,V3,3/6] dm: ignore discard return value
    (no matching commit)
  - [f2fs-dev,V3,4/6] nvmet: ignore discard return value
    (no matching commit)
  - [f2fs-dev,V3,5/6] f2fs: ignore discard return value
    (no matching commit)
  - [f2fs-dev,V3,6/6] xfs: ignore discard return value
    (no matching commit)

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



WARNING: multiple messages have this Message-ID (diff)
From: patchwork-bot+f2fs--- via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: Chaitanya Kulkarni <ckulkarnilinux@gmail.com>
Cc: axboe@kernel.dk, dm-devel@lists.linux.dev, kch@nvidia.com,
	sagi@grimberg.me, linux-xfs@vger.kernel.org,
	linux-block@vger.kernel.org, cem@kernel.org, snitzer@kernel.org,
	linux-kernel@vger.kernel.org, linux-nvme@lists.infradead.org,
	linux-f2fs-devel@lists.sourceforge.net,
	linux-raid@vger.kernel.org, song@kernel.org, mpatocka@redhat.com,
	jaegeuk@kernel.org, bpf@vger.kernel.org, yukuai@fnnas.com,
	hch@lst.de, agk@redhat.com
Subject: Re: [f2fs-dev] [PATCH V3 0/6] block: ignore __blkdev_issue_discard() ret value
Date: Tue, 09 Dec 2025 17:18:47 +0000	[thread overview]
Message-ID: <176530072781.4018985.3920629164173659180.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251124234806.75216-1-ckulkarnilinux@gmail.com>

Hello:

This series was applied to jaegeuk/f2fs.git (dev)
by Jens Axboe <axboe@kernel.dk>:

On Mon, 24 Nov 2025 15:48:00 -0800 you wrote:
> Hi,
> 
> __blkdev_issue_discard() only returns value 0, that makes post call
> error checking code dead. This patch series revmoes this dead code at
> all the call sites and adjust the callers.
> 
> Please note that it doesn't change the return type of the function from
> int to void in this series, it will be done once this series gets merged
> smoothly.
> 
> [...]

Here is the summary with links:
  - [f2fs-dev,V3,1/6] block: ignore discard return value
    https://git.kernel.org/jaegeuk/f2fs/c/7d09a8e25121
  - [f2fs-dev,V3,2/6] md: ignore discard return value
    (no matching commit)
  - [f2fs-dev,V3,3/6] dm: ignore discard return value
    (no matching commit)
  - [f2fs-dev,V3,4/6] nvmet: ignore discard return value
    (no matching commit)
  - [f2fs-dev,V3,5/6] f2fs: ignore discard return value
    (no matching commit)
  - [f2fs-dev,V3,6/6] xfs: ignore discard return value
    (no matching commit)

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html




_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel

  parent reply	other threads:[~2025-12-09 17:21 UTC|newest]

Thread overview: 73+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-24 23:48 [PATCH V3 0/6] block: ignore __blkdev_issue_discard() ret value Chaitanya Kulkarni
2025-11-24 23:48 ` [f2fs-dev] " Chaitanya Kulkarni
2025-11-24 23:48 ` [PATCH V3 1/6] block: ignore discard return value Chaitanya Kulkarni
2025-11-24 23:48   ` [f2fs-dev] " Chaitanya Kulkarni
2025-11-25 17:38   ` Jens Axboe
2025-11-25 17:38     ` [f2fs-dev] " Jens Axboe
2025-11-25 19:09     ` Chaitanya Kulkarni
2025-11-25 19:09       ` [f2fs-dev] " Chaitanya Kulkarni
2025-11-25 19:19       ` Jens Axboe
2025-11-25 19:19         ` [f2fs-dev] " Jens Axboe
2025-11-24 23:48 ` [PATCH V3 2/6] md: " Chaitanya Kulkarni
2025-11-24 23:48   ` [f2fs-dev] " Chaitanya Kulkarni
2025-12-01  6:22   ` Chaitanya Kulkarni
2026-01-24 21:29     ` Chaitanya Kulkarni
2025-11-24 23:48 ` [PATCH V3 3/6] dm: " Chaitanya Kulkarni
2025-11-24 23:48   ` [f2fs-dev] " Chaitanya Kulkarni
2025-12-01  6:23   ` Chaitanya Kulkarni
2025-12-01 21:07     ` Mikulas Patocka
2025-11-24 23:48 ` [PATCH V3 4/6] nvmet: " Chaitanya Kulkarni
2025-11-24 23:48   ` [f2fs-dev] " Chaitanya Kulkarni
2025-11-26 10:14   ` Yongpeng Yang
2025-11-26 10:14     ` Yongpeng Yang
2025-11-26 10:37     ` Christoph Hellwig
2025-11-26 10:37       ` Christoph Hellwig
2026-01-24 21:35   ` Chaitanya Kulkarni
2026-01-24 21:35     ` [f2fs-dev] " Chaitanya Kulkarni via Linux-f2fs-devel
2026-01-26  4:57     ` hch
2026-01-26  4:57       ` [f2fs-dev] " hch
2026-01-27 22:40       ` Chaitanya Kulkarni
2026-01-27 22:40         ` [f2fs-dev] " Chaitanya Kulkarni via Linux-f2fs-devel
2025-11-24 23:48 ` [PATCH V3 5/6] f2fs: " Chaitanya Kulkarni
2025-11-24 23:48   ` [f2fs-dev] " Chaitanya Kulkarni
2025-11-25  1:10   ` Chao Yu
2025-11-25  1:10     ` [f2fs-dev] " Chao Yu via Linux-f2fs-devel
2025-11-25  6:33     ` Christoph Hellwig
2025-11-25  6:33       ` [f2fs-dev] " Christoph Hellwig
2025-11-25  7:11       ` Chao Yu
2025-11-25  7:11         ` [f2fs-dev] " Chao Yu via Linux-f2fs-devel
2025-12-01  6:26         ` Chaitanya Kulkarni via Linux-f2fs-devel
2025-11-26  2:47   ` Chao Yu
2025-11-26  2:47     ` [f2fs-dev] " Chao Yu via Linux-f2fs-devel
2025-11-26  3:37     ` Chaitanya Kulkarni
2025-11-26  3:37       ` [f2fs-dev] " Chaitanya Kulkarni via Linux-f2fs-devel
2025-11-26  3:58       ` Chao Yu
2025-11-26  3:58         ` [f2fs-dev] " Chao Yu via Linux-f2fs-devel
2025-11-24 23:48 ` [PATCH V3 6/6] xfs: " Chaitanya Kulkarni
2025-11-24 23:48   ` [f2fs-dev] " Chaitanya Kulkarni
2025-11-26  2:37   ` Yongpeng Yang
2025-11-26  2:37     ` Yongpeng Yang
2025-11-26  8:07     ` Chaitanya Kulkarni
2025-11-26  8:07       ` Chaitanya Kulkarni via Linux-f2fs-devel
2025-11-26  9:14       ` Yongpeng Yang
2025-11-26  9:14         ` Yongpeng Yang
2025-11-26  9:48         ` Yongpeng Yang
2025-11-26  9:48           ` Yongpeng Yang
2025-11-26 10:34       ` hch
2025-11-26 10:34         ` hch
2025-11-26 10:33     ` Christoph Hellwig
2025-11-26 10:33       ` Christoph Hellwig
2025-12-01  6:28   ` Chaitanya Kulkarni
2025-12-01 12:20     ` Carlos Maiolino
2025-11-25 13:20 ` [PATCH V3 0/6] block: ignore __blkdev_issue_discard() ret value Anuj gupta
2025-11-25 13:20   ` [f2fs-dev] " Anuj gupta
2025-11-25 19:20 ` (subset) " Jens Axboe
2025-11-25 19:20   ` [f2fs-dev] " Jens Axboe
2025-12-03 21:50 ` [f2fs-dev] " patchwork-bot+f2fs
2025-12-03 21:50   ` patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-12-09 17:18 ` patchwork-bot+f2fs [this message]
2025-12-09 17:18   ` patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-12-16  0:50 ` patchwork-bot+f2fs
2025-12-16  0:50   ` patchwork-bot+f2fs--- via Linux-f2fs-devel
2026-02-17 21:14 ` patchwork-bot+f2fs
2026-02-17 21:14   ` patchwork-bot+f2fs--- via Linux-f2fs-devel

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=176530072781.4018985.3920629164173659180.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+f2fs@kernel.org \
    --cc=agk@redhat.com \
    --cc=axboe@kernel.dk \
    --cc=bpf@vger.kernel.org \
    --cc=cem@kernel.org \
    --cc=chao@kernel.org \
    --cc=ckulkarnilinux@gmail.com \
    --cc=dm-devel@lists.linux.dev \
    --cc=hch@lst.de \
    --cc=jaegeuk@kernel.org \
    --cc=kch@nvidia.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=mpatocka@redhat.com \
    --cc=sagi@grimberg.me \
    --cc=snitzer@kernel.org \
    --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 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.