From: Sergei Shtepa <sergei.shtepa@veeam.com>
To: Christoph Hellwig <hch@infradead.org>,
Hannes Reinecke <hare@suse.de>, Mike Snitzer <snitzer@redhat.com>,
Alasdair Kergon <agk@redhat.com>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Jens Axboe <axboe@kernel.dk>,
"dm-devel@redhat.com" <dm-devel@redhat.com>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: Pavel Tide <Pavel.TIde@veeam.com>
Subject: Re: [PATCH v9 0/4] block device interposer
Date: Mon, 21 Jun 2021 13:41:31 +0300 [thread overview]
Message-ID: <20210621104131.GA8841@veeam.com> (raw)
In-Reply-To: <1619023545-23431-1-git-send-email-sergei.shtepa@veeam.com>
Hi Mike,
This is a follow up message.
Did you have a chance to take a look at the latest patchset from April?
Thanks!
I can update the patch to be compatible with kernel 5.14.
I would like to know if you still have interest in blk_interposer.
--
Sergei Shtepa
Veeam Software developer.
WARNING: multiple messages have this Message-ID (diff)
From: Sergei Shtepa <sergei.shtepa@veeam.com>
To: Christoph Hellwig <hch@infradead.org>,
Hannes Reinecke <hare@suse.de>, Mike Snitzer <snitzer@redhat.com>,
Alasdair Kergon <agk@redhat.com>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Jens Axboe <axboe@kernel.dk>,
"dm-devel@redhat.com" <dm-devel@redhat.com>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: Pavel Tide <Pavel.TIde@veeam.com>
Subject: Re: [dm-devel] [PATCH v9 0/4] block device interposer
Date: Mon, 21 Jun 2021 13:41:31 +0300 [thread overview]
Message-ID: <20210621104131.GA8841@veeam.com> (raw)
In-Reply-To: <1619023545-23431-1-git-send-email-sergei.shtepa@veeam.com>
Hi Mike,
This is a follow up message.
Did you have a chance to take a look at the latest patchset from April?
Thanks!
I can update the patch to be compatible with kernel 5.14.
I would like to know if you still have interest in blk_interposer.
--
Sergei Shtepa
Veeam Software developer.
--
dm-devel mailing list
dm-devel@redhat.com
https://listman.redhat.com/mailman/listinfo/dm-devel
next prev parent reply other threads:[~2021-06-21 10:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-21 16:45 [PATCH v9 0/4] block device interposer Sergei Shtepa
2021-04-21 16:45 ` [dm-devel] " Sergei Shtepa
2021-04-21 16:45 ` [PATCH v9 1/4] Adds blk_interposer Sergei Shtepa
2021-04-21 16:45 ` [dm-devel] " Sergei Shtepa
2021-04-21 16:45 ` [PATCH v9 2/4] Applying the blk_interposer in the block device layer Sergei Shtepa
2021-04-21 16:45 ` [dm-devel] " Sergei Shtepa
2021-04-21 16:45 ` [PATCH v9 3/4] Add blk_interposer in DM Sergei Shtepa
2021-04-21 16:45 ` [dm-devel] " Sergei Shtepa
2021-04-21 16:45 ` [PATCH v9 4/4] Using dm_get_device_ex() instead of dm_get_device() Sergei Shtepa
2021-04-21 16:45 ` [dm-devel] " Sergei Shtepa
2021-06-21 10:41 ` Sergei Shtepa [this message]
2021-06-21 10:41 ` [dm-devel] [PATCH v9 0/4] block device interposer Sergei Shtepa
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=20210621104131.GA8841@veeam.com \
--to=sergei.shtepa@veeam.com \
--cc=Pavel.TIde@veeam.com \
--cc=agk@redhat.com \
--cc=axboe@kernel.dk \
--cc=dm-devel@redhat.com \
--cc=hare@suse.de \
--cc=hch@infradead.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=snitzer@redhat.com \
--cc=viro@zeniv.linux.org.uk \
/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.