From: "Christoph Böhmwalder" <christoph.boehmwalder@linbit.com>
To: Jens Axboe <axboe@kernel.dk>,
Colin Ian King <colin.i.king@gmail.com>,
Philipp Reisner <philipp.reisner@linbit.com>,
Lars Ellenberg <lars.ellenberg@linbit.com>,
drbd-dev@lists.linbit.com, linux-block@vger.kernel.org
Cc: kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH][next] drbd: Fix typos: "receive_peer_dagatg" -> "receive_peer_dagtag"
Date: Wed, 18 Mar 2026 22:13:52 +0100 [thread overview]
Message-ID: <f67a657b-bec5-404f-9435-a69f11b7e396@linbit.com> (raw)
In-Reply-To: <ea558bc4-3efe-4eca-9da6-56f4a5302056@kernel.dk>
Am 18.03.26 um 20:05 schrieb Jens Axboe:
> On 3/16/26 2:25 PM, Colin Ian King wrote:
>> There are a couple of typos in drbd_info and drbd_err messages.
>> Fix them.
>
> Doesn't apply against for-next?
>
This is against the drbd-next tree, which is included in linux-next
since a few days.
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/tree/Next/Trees#n267
I realize this is a bit awkward, since there is no way to really know
which patches target linux-next and which block/for-next.
Is there any specific way we could handle this to make it easier for you?
--
Christoph Böhmwalder
LINBIT | Keeping the Digital World Running
DRBD HA — Disaster Recovery — Software defined Storage
next prev parent reply other threads:[~2026-03-18 21:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-16 20:25 [PATCH][next] drbd: Fix typos: "receive_peer_dagatg" -> "receive_peer_dagtag" Colin Ian King
2026-03-18 19:05 ` Jens Axboe
2026-03-18 21:13 ` Christoph Böhmwalder [this message]
2026-03-18 21:20 ` Jens Axboe
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=f67a657b-bec5-404f-9435-a69f11b7e396@linbit.com \
--to=christoph.boehmwalder@linbit.com \
--cc=axboe@kernel.dk \
--cc=colin.i.king@gmail.com \
--cc=drbd-dev@lists.linbit.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=lars.ellenberg@linbit.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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