public inbox for kernel-janitors@vger.kernel.org
 help / color / mirror / Atom feed
* [PATCH][next] drbd: Fix typos: "receive_peer_dagatg" -> "receive_peer_dagtag"
@ 2026-03-16 20:25 Colin Ian King
  2026-03-18 19:05 ` Jens Axboe
  0 siblings, 1 reply; 4+ messages in thread
From: Colin Ian King @ 2026-03-16 20:25 UTC (permalink / raw)
  To: Philipp Reisner, Lars Ellenberg, Christoph Böhmwalder,
	Jens Axboe, drbd-dev, linux-block
  Cc: kernel-janitors, linux-kernel

There are a couple of typos in drbd_info and drbd_err messages.
Fix them.

Signed-off-by: Colin Ian King <colin.i.king@gmail.com>
---
 drivers/block/drbd/drbd_receiver.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/drivers/block/drbd/drbd_receiver.c b/drivers/block/drbd/drbd_receiver.c
index 06d83b5ffafb..100207623182 100644
--- a/drivers/block/drbd/drbd_receiver.c
+++ b/drivers/block/drbd/drbd_receiver.c
@@ -8850,14 +8850,14 @@ static int receive_peer_dagtag(struct drbd_connection *connection, struct packet
 			    strategy != SYNC_SOURCE_USE_BITMAP &&
 			    strategy != SYNC_TARGET_USE_BITMAP) {
 				drbd_info(peer_device,
-					  "receive_peer_dagatg(): %s by rule=%s\n",
+					  "receive_peer_dagtag(): %s by rule=%s\n",
 					  strategy_descriptor(strategy).name,
 					  drbd_sync_rule_str(rule));
 				goto out;
 			}
 		} else if (ps != strategy) {
 			drbd_err(peer_device,
-				 "receive_peer_dagatg(): Inconsistent resync directions %s %s\n",
+				 "receive_peer_dagtag(): Inconsistent resync directions %s %s\n",
 				 strategy_descriptor(strategy).name, strategy_descriptor(ps).name);
 			goto out;
 		}
-- 
2.53.0


^ permalink raw reply related	[flat|nested] 4+ messages in thread

* Re: [PATCH][next] drbd: Fix typos: "receive_peer_dagatg" -> "receive_peer_dagtag"
  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
  0 siblings, 1 reply; 4+ messages in thread
From: Jens Axboe @ 2026-03-18 19:05 UTC (permalink / raw)
  To: Colin Ian King, Philipp Reisner, Lars Ellenberg,
	Christoph Böhmwalder, drbd-dev, linux-block
  Cc: kernel-janitors, linux-kernel

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?

-- 
Jens Axboe


^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [PATCH][next] drbd: Fix typos: "receive_peer_dagatg" -> "receive_peer_dagtag"
  2026-03-18 19:05 ` Jens Axboe
@ 2026-03-18 21:13   ` Christoph Böhmwalder
  2026-03-18 21:20     ` Jens Axboe
  0 siblings, 1 reply; 4+ messages in thread
From: Christoph Böhmwalder @ 2026-03-18 21:13 UTC (permalink / raw)
  To: Jens Axboe, Colin Ian King, Philipp Reisner, Lars Ellenberg,
	drbd-dev, linux-block
  Cc: kernel-janitors, linux-kernel



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


^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [PATCH][next] drbd: Fix typos: "receive_peer_dagatg" -> "receive_peer_dagtag"
  2026-03-18 21:13   ` Christoph Böhmwalder
@ 2026-03-18 21:20     ` Jens Axboe
  0 siblings, 0 replies; 4+ messages in thread
From: Jens Axboe @ 2026-03-18 21:20 UTC (permalink / raw)
  To: Christoph Böhmwalder, Colin Ian King, Philipp Reisner,
	Lars Ellenberg, drbd-dev, linux-block
  Cc: kernel-janitors, linux-kernel

On 3/18/26 3:13 PM, Christoph Böhmwalder wrote:
> 
> 
> 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?

Yes, send the patches so they end up in the block tree rather than add
another tree.

-- 
Jens Axboe


^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2026-03-18 21:20 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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
2026-03-18 21:20     ` Jens Axboe

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox