From: Mikulas Patocka <mpatocka@redhat.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: Li Nan <linan666@huaweicloud.com>,
Zdenek Kabelac <zkabelac@redhat.com>,
Christoph Hellwig <hch@infradead.org>,
Chaitanya Kulkarni <chaitanyak@nvidia.com>,
linux-block@vger.kernel.org, dm-devel@redhat.com
Subject: Re: [PATCH v3 0/4] brd discard patches
Date: Tue, 14 Nov 2023 14:59:54 +0100 (CET) [thread overview]
Message-ID: <c2653ea-b4ab-4131-50f1-82e450633194@redhat.com> (raw)
In-Reply-To: <c1955b5b-4980-55dd-a1b7-54c19831d9d2@huaweicloud.com>
[-- Attachment #1: Type: text/plain, Size: 722 bytes --]
On Fri, 10 Nov 2023, Li Nan wrote:
> friendly ping...
Jens? Do you want this patch series or not?
Mikulas
> 在 2023/8/10 18:07, Mikulas Patocka 写道:
> > Hi
> >
> > Here I'm submitting the ramdisk discard patches for the next merge window.
> > If you want to make some more changes, please let me now.
> >
> > Changes since version 2:
> > There are no functional changes, I only moved the switch statement
> > conversion to a separate patch, so that it's easier to review.
> >
> > Patch 1: introduce a switch statement in brd_submit_bio
> > Patch 2: extend the rcu regions to cover read and write
> > Patch 3: enable discard
> > Patch 4: implement write zeroes
> >
> > Mikulas
> >
>
> --
> Thanks,
> Nan
>
next prev parent reply other threads:[~2023-11-14 14:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-10 10:07 [PATCH v3 0/4] brd discard patches Mikulas Patocka
2023-08-10 10:08 ` [PATCH v3 1/4] brd: use a switch statement in brd_submit_bio Mikulas Patocka
2023-08-10 10:09 ` [PATCH v3 2/4] brd: extend the rcu regions to cover read and write Mikulas Patocka
2023-08-10 10:09 ` [PATCH v3 3/4] brd: enable discard Mikulas Patocka
2023-08-10 10:10 ` [PATCH v3 4/4] brd: implement write zeroes Mikulas Patocka
2023-11-10 1:22 ` [PATCH v3 0/4] brd discard patches Li Nan
2023-11-14 13:59 ` Mikulas Patocka [this message]
2024-01-19 8:41 ` Ming Lei
2024-01-22 16:30 ` Mikulas Patocka
2024-01-23 2:49 ` Ming Lei
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=c2653ea-b4ab-4131-50f1-82e450633194@redhat.com \
--to=mpatocka@redhat.com \
--cc=axboe@kernel.dk \
--cc=chaitanyak@nvidia.com \
--cc=dm-devel@redhat.com \
--cc=hch@infradead.org \
--cc=linan666@huaweicloud.com \
--cc=linux-block@vger.kernel.org \
--cc=zkabelac@redhat.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