Distributed Replicated Block Device (DRBD) development
 help / color / mirror / Atom feed
From: "Christoph Böhmwalder" <christoph.boehmwalder@linbit.com>
To: Ruslan Vagner <rusya92266@gmail.com>
Cc: drbd-dev@lists.linux.dev, philipp.reisner@linbit.com,
	lars.ellenberg@linbit.com
Subject: Re: [PATCH] drbd: fix comment typo in drbd_state.c
Date: Tue, 15 Sep 2026 17:11:13 +0200	[thread overview]
Message-ID: <a43bdc79-aacd-41e9-88a9-2a73b3a3105c@linbit.com> (raw)
In-Reply-To: <CAF9RqJ6eqNCnJYfqGRyZ4N7jO6nzVvHZhzuAkR=D+ELeriq_=w@mail.gmail.com>



Am 15.09.26 um 14:55 schrieb Ruslan Vagner:
> Fix the spelling in comments. No functional change.
> 
> Signed-off-by: Ruslan Vagner <rusya92266@gmail.com>
> ---
>  drivers/block/drbd/drbd_state.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/block/drbd/drbd_state.c b/drivers/block/drbd/drbd_state.c
> index adcba7f1d8ea..98abd2351d6d 100644
> --- a/drivers/block/drbd/drbd_state.c
> +++ b/drivers/block/drbd/drbd_state.c
> @@ -1339,7 +1339,7 @@ _drbd_set_state(struct drbd_device *device,
> union drbd_state ns,
> 
>  	remember_new_state(state_change);
> 
> -	/* put replicated vs not-replicated requests in seperate epochs */
> +	/* put replicated vs not-replicated requests in separate epochs */
>  	if (drbd_should_do_remote((union drbd_dev_state)os.i) !=
>  	    drbd_should_do_remote((union drbd_dev_state)ns.i))
>  		start_new_tl_epoch(connection);

Typo fixes like this are usually only worth it if they come with "real"
fixes in the same general area. Otherwise, they just cause unneccessary
churn for the involved maintainers.

Regards,
Christoph

-- 
Christoph Böhmwalder
LINBIT | Keeping the Digital World Running
DRBD HA —  Disaster Recovery — Software defined Storage


      reply	other threads:[~2026-09-15 15:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-15 12:55 [PATCH] drbd: fix comment typo in drbd_state.c Ruslan Vagner
2026-09-15 15:11 ` Christoph Böhmwalder [this message]

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=a43bdc79-aacd-41e9-88a9-2a73b3a3105c@linbit.com \
    --to=christoph.boehmwalder@linbit.com \
    --cc=drbd-dev@lists.linux.dev \
    --cc=lars.ellenberg@linbit.com \
    --cc=philipp.reisner@linbit.com \
    --cc=rusya92266@gmail.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