From: Sergei Shtepa <sergei.shtepa@veeam.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: "masahiroy@kernel.org" <masahiroy@kernel.org>,
"michal.lkml@markovi.net" <michal.lkml@markovi.net>,
"koct9i@gmail.com" <koct9i@gmail.com>,
"jack@suse.cz" <jack@suse.cz>,
"damien.lemoal@wdc.com" <damien.lemoal@wdc.com>,
"ming.lei@redhat.com" <ming.lei@redhat.com>,
"steve@sk2.org" <steve@sk2.org>,
"linux-kbuild@vger.kernel.org" <linux-kbuild@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>
Subject: Re: [PATCH 0/1] block io layer filters api
Date: Tue, 1 Sep 2020 19:35:27 +0300 [thread overview]
Message-ID: <20200901163240.GA18490@veeam.com> (raw)
In-Reply-To: <722e85ac-f494-2cb3-4caf-d903d79a5645@kernel.dk>
Jens, thank you so much for your prompt response and clarification on your
position.
We’re totally committed to having the upstream driver as the canonical version,
and to maintaining it.
It was probably a mistake not to build it like that right away considering it
has always been our vision, but frankly speaking we were simply too shy to go
this route when we first started 4 years ago, with just a handful of users and
an unclear demand/future. But now in 2020, it’s a different story.
We’ll get started on the in-tree kernel mode right away, and will reconvene
once ready.
--
Sergei Shtepa
Veeam Software developer.
next prev parent reply other threads:[~2020-09-01 16:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-27 19:13 [PATCH 0/1] block io layer filters api Sergei Shtepa
2020-08-27 19:13 ` [PATCH 1/1] " Sergei Shtepa
2020-08-28 7:24 ` [PATCH 0/1] " Damien Le Moal
2020-08-28 13:54 ` Jens Axboe
2020-09-01 13:29 ` Sergei Shtepa
2020-09-01 14:49 ` Jens Axboe
2020-09-01 16:35 ` Sergei Shtepa [this message]
2020-09-01 15:34 ` Bart Van Assche
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=20200901163240.GA18490@veeam.com \
--to=sergei.shtepa@veeam.com \
--cc=axboe@kernel.dk \
--cc=damien.lemoal@wdc.com \
--cc=jack@suse.cz \
--cc=koct9i@gmail.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=michal.lkml@markovi.net \
--cc=ming.lei@redhat.com \
--cc=steve@sk2.org \
/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.