Distributed Replicated Block Device (DRBD) development
 help / color / mirror / Atom feed
From: "Christoph Böhmwalder" <christoph.boehmwalder@linbit.com>
To: Sukrut Heroorkar <hsukrut3@gmail.com>,
	Philipp Reisner <philipp.reisner@linbit.com>,
	Lars Ellenberg <lars.ellenberg@linbit.com>,
	Jens Axboe <axboe@kernel.dk>,
	"open list:DRBD DRIVER" <drbd-dev@lists.linbit.com>,
	"open list:BLOCK LAYER" <linux-block@vger.kernel.org>,
	open list <linux-kernel@vger.kernel.org>
Cc: shuah@kernel.org, david.hunter.linux@gmail.com
Subject: Re: [PATCH] drbd: turn bitmap I/O comments into regular block comments
Date: Tue, 18 Nov 2025 11:51:02 +0100	[thread overview]
Message-ID: <11f8aaaa-b5de-44dc-9263-5bdb506923ac@linbit.com> (raw)
In-Reply-To: <20251118090753.390818-1-hsukrut3@gmail.com>

Am 18.11.25 um 10:07 schrieb Sukrut Heroorkar:
> W=1 build warns because the bitmap I/O comments use '/**', which
> marks them as kernel-doc comments even though these functions do not
> document an external API.
> 
> Convert these comments to regular block comments so kernel-doc no
> longer parses them.
> 
> Signed-off-by: Sukrut Heroorkar <hsukrut3@gmail.com>
> ---
> See: https://lore.kernel.org/all/20251117172557.355797-1-hsukrut3@gmail.com/t/
> 
>  drivers/block/drbd/drbd_bitmap.c | 10 +++++-----
>  1 file changed, 5 insertions(+), 5 deletions(-)

Thanks.

Acked-by: Christoph Böhmwalder <christoph.boehmwalder@linbit.com>

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


  reply	other threads:[~2025-11-18 10:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-18  9:07 [PATCH] drbd: turn bitmap I/O comments into regular block comments Sukrut Heroorkar
2025-11-18 10:51 ` Christoph Böhmwalder [this message]
2025-11-18 15:38 ` 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=11f8aaaa-b5de-44dc-9263-5bdb506923ac@linbit.com \
    --to=christoph.boehmwalder@linbit.com \
    --cc=axboe@kernel.dk \
    --cc=david.hunter.linux@gmail.com \
    --cc=drbd-dev@lists.linbit.com \
    --cc=hsukrut3@gmail.com \
    --cc=lars.ellenberg@linbit.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=philipp.reisner@linbit.com \
    --cc=shuah@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox