From: Eric Biggers <ebiggers@kernel.org>
To: Bart Van Assche <bvanassche@acm.org>
Cc: Milan Broz <gmazyland@gmail.com>,
dm-devel@lists.linux.dev, Alasdair Kergon <agk@redhat.com>,
Mike Snitzer <snitzer@kernel.org>,
Mikulas Patocka <mpatocka@redhat.com>,
linux-kernel@vger.kernel.org,
Gilad Ben-Yossef <gilad@benyossef.com>,
Ard Biesheuvel <ardb@kernel.org>,
"Jason A . Donenfeld" <Jason@zx2c4.com>,
Sami Tolvanen <samitolvanen@google.com>
Subject: Re: [PATCH v2] dm-verity: remove support for asynchronous hashes
Date: Thu, 10 Jul 2025 16:04:47 +0000 [thread overview]
Message-ID: <20250710160447.GA604603@google.com> (raw)
In-Reply-To: <48bd1925-94b6-4913-9cbc-f348e4dc4ae6@acm.org>
On Thu, Jul 10, 2025 at 08:55:31AM -0700, Bart Van Assche wrote:
> On 7/10/25 1:28 AM, Milan Broz wrote:
> > Just one nitpick - could you please increase minor version of dm-
> > verity target, so we have information in debug log that it is a
> > patched version?
> Others are convinced that version numbers have no place in the upstream
> kernel and that all version information should be removed from upstream
> kernel drivers.
As long as it's there, we might as well update it. But yes, the
device-mapper version numbers don't work all that well.
- Eric
next prev parent reply other threads:[~2025-07-10 16:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-09 19:09 [PATCH v2] dm-verity: remove support for asynchronous hashes Eric Biggers
2025-07-10 8:28 ` Milan Broz
2025-07-10 15:55 ` Bart Van Assche
2025-07-10 16:04 ` Eric Biggers [this message]
2025-07-10 16:18 ` Milan Broz
2025-07-10 16:10 ` Eric Biggers
2025-07-10 19:38 ` Milan Broz
2025-07-10 18:08 ` Eric Biggers
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=20250710160447.GA604603@google.com \
--to=ebiggers@kernel.org \
--cc=Jason@zx2c4.com \
--cc=agk@redhat.com \
--cc=ardb@kernel.org \
--cc=bvanassche@acm.org \
--cc=dm-devel@lists.linux.dev \
--cc=gilad@benyossef.com \
--cc=gmazyland@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mpatocka@redhat.com \
--cc=samitolvanen@google.com \
--cc=snitzer@kernel.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.