From: "hch@lst.de" <hch@lst.de>
To: Dongyang Li <dongyangli@ddn.com>
Cc: "joshi.k@samsung.com" <joshi.k@samsung.com>,
"martin.petersen@oracle.com" <martin.petersen@oracle.com>,
"hch@lst.de" <hch@lst.de>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
"axboe@kernel.dk" <axboe@kernel.dk>,
"josef@toxicpanda.com" <josef@toxicpanda.com>,
"lsf-pc@lists.linux-foundation.org"
<lsf-pc@lists.linux-foundation.org>,
"kbusch@kernel.org" <kbusch@kernel.org>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>
Subject: Re: [Lsf-pc] [LSF/MM/BPF ATTEND][LSF/MM/BPF TOPIC] Meta/Integrity/PI improvements
Date: Wed, 3 Apr 2024 14:42:55 +0200 [thread overview]
Message-ID: <20240403124255.GA19272@lst.de> (raw)
In-Reply-To: <d442fe43e7b43d9e00c168f91dcfddd5a240b366.camel@ddn.com>
In kernel use is easy, we can do that as soon as the first in-kernel
user comes along. Which one do you have in mind?
next prev parent reply other threads:[~2024-04-03 12:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20240222193304epcas5p318426c5267ee520e6b5710164c533b7d@epcas5p3.samsung.com>
2024-02-22 19:33 ` [LSF/MM/BPF ATTEND][LSF/MM/BPF TOPIC] Meta/Integrity/PI improvements Kanchan Joshi
2024-02-22 20:08 ` Keith Busch
2024-02-23 12:41 ` Kanchan Joshi
2024-02-23 14:38 ` David Sterba
2024-02-26 23:15 ` [Lsf-pc] " Martin K. Petersen
2024-03-27 13:45 ` Kanchan Joshi
2024-03-28 0:30 ` Martin K. Petersen
2024-03-29 11:35 ` Kanchan Joshi
2024-04-03 2:10 ` Martin K. Petersen
2024-04-02 10:45 ` Dongyang Li
2024-04-02 11:37 ` Hannes Reinecke
2024-04-02 16:52 ` Kanchan Joshi
2024-04-03 12:40 ` Dongyang Li
2024-04-03 12:42 ` hch [this message]
2024-04-04 9:53 ` Dongyang Li
2024-04-05 6:12 ` Kent Overstreet
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=20240403124255.GA19272@lst.de \
--to=hch@lst.de \
--cc=axboe@kernel.dk \
--cc=dongyangli@ddn.com \
--cc=josef@toxicpanda.com \
--cc=joshi.k@samsung.com \
--cc=kbusch@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=martin.petersen@oracle.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.