From: Christoph Hellwig <hch@infradead.org>
To: Fabio Fantoni <fantonifabio@tiscali.it>
Cc: corbet@lwn.net, axboe@kernel.dk, linux-block@vger.kernel.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
Sergei Shtepa <sergei.shtepa@veeam.com>
Subject: Re: [PATCH v2] documentation: fix Generic Block Device Capability
Date: Mon, 16 Jan 2023 09:53:24 -0800 [thread overview]
Message-ID: <Y8WPFMFxpfdZKs5a@infradead.org> (raw)
In-Reply-To: <20230110132104.12499-1-fantonifabio@tiscali.it>
On Tue, Jan 10, 2023 at 02:21:04PM +0100, Fabio Fantoni wrote:
> - * ``GENHD_FL_REMOVABLE``: indicates that the block device gives access to
> + * ``GENHD_FL_REMOVABLE`` (0x01): indicates that the block device gives access to
The numberic values really do not belong into the documentation. They
are just implementation details.
next prev parent reply other threads:[~2023-01-16 18:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-10 13:21 [PATCH v2] documentation: fix Generic Block Device Capability Fabio Fantoni
2023-01-16 17:53 ` Christoph Hellwig [this message]
2023-01-16 18:14 ` Fabio Fantoni
2023-01-17 6:05 ` Christoph Hellwig
2023-01-17 15:51 ` Fabio Fantoni
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=Y8WPFMFxpfdZKs5a@infradead.org \
--to=hch@infradead.org \
--cc=axboe@kernel.dk \
--cc=corbet@lwn.net \
--cc=fantonifabio@tiscali.it \
--cc=linux-block@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sergei.shtepa@veeam.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;
as well as URLs for NNTP newsgroup(s).