From: "Arnd Bergmann" <arnd@arndb.de>
To: "Christoph Böhmwalder" <christoph.boehmwalder@linbit.com>,
"Arnd Bergmann" <arnd@kernel.org>,
"Philipp Reisner" <philipp.reisner@linbit.com>,
"Lars Ellenberg" <lars.ellenberg@linbit.com>,
"Jens Axboe" <axboe@kernel.dk>,
"David S . Miller" <davem@davemloft.net>,
"Eric Dumazet" <edumazet@google.com>,
"Jakub Kicinski" <kuba@kernel.org>,
"Paolo Abeni" <pabeni@redhat.com>
Cc: Eric Biggers <ebiggers@google.com>,
Netdev <netdev@vger.kernel.org>,
linux-kernel@vger.kernel.org, linux-block@vger.kernel.org,
Simon Horman <horms@kernel.org>,
drbd-dev@lists.linbit.com
Subject: Re: [PATCH 2/2] drbd: select CONFIG_NET_HANDSHAKE
Date: Wed, 18 Mar 2026 22:20:49 +0100 [thread overview]
Message-ID: <74946481-4eb7-4d8d-b10a-881ebd84ee33@app.fastmail.com> (raw)
In-Reply-To: <6b696861-ac39-4a87-a2fa-ad47a75031c6@linbit.com>
On Wed, Mar 18, 2026, at 22:16, Christoph Böhmwalder wrote:
> Am 18.03.26 um 11:48 schrieb Arnd Bergmann:
>> config NET_HANDSHAKE_KUNIT_TEST
>> tristate "KUnit tests for the handshake upcall mechanism" if !KUNIT_ALL_TESTS
>
> Thanks for the fix, I applied it to our drbd-next tree (which should end
> up in linux-next).
>
> I would prefer to squash these kinds of fixups to keep the history in
> our patch series clean.
> Arnd, does that work for you? How do you prefer we handle attribution?
>
> Unfortunately I couldn't really find a clear precedence pattern for
> this, how is this usually handled?
Whichever way works best for you. Some people care a lot about
attribution for bugfixes, but I generally prefer a clean history
myself.
Arnd
next prev parent reply other threads:[~2026-03-18 21:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-18 10:48 [PATCH 1/2] drbd: fix rdma dependency Arnd Bergmann
2026-03-18 10:48 ` [PATCH 2/2] drbd: select CONFIG_NET_HANDSHAKE Arnd Bergmann
2026-03-18 21:16 ` Christoph Böhmwalder
2026-03-18 21:20 ` Arnd Bergmann [this message]
2026-03-18 15:24 ` [PATCH 1/2] drbd: fix rdma dependency Christoph Böhmwalder
2026-03-18 15:31 ` Arnd Bergmann
2026-03-18 15:36 ` Christoph Böhmwalder
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=74946481-4eb7-4d8d-b10a-881ebd84ee33@app.fastmail.com \
--to=arnd@arndb.de \
--cc=arnd@kernel.org \
--cc=axboe@kernel.dk \
--cc=christoph.boehmwalder@linbit.com \
--cc=davem@davemloft.net \
--cc=drbd-dev@lists.linbit.com \
--cc=ebiggers@google.com \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=lars.ellenberg@linbit.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=philipp.reisner@linbit.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