From: Jonathan Corbet <corbet@lwn.net>
To: Aishwarya Pant <aishpant@gmail.com>
Cc: linux-block@vger.kernel.org, Julia Lawall <julia.lawall@lip6.fr>,
linux-kernel@vger.kernel.org,
Greg KH <gregkh@linuxfoundation.org>,
linux-doc@vger.kernel.org
Subject: Re: [PATCH v2] block/loop: add documentation for sysfs interface
Date: Fri, 23 Feb 2018 08:20:29 -0700 [thread overview]
Message-ID: <20180223082029.731acffd@lwn.net> (raw)
In-Reply-To: <20180217061304.GA14083@mordor.localdomain>
On Sat, 17 Feb 2018 11:43:04 +0530
Aishwarya Pant <aishpant@gmail.com> wrote:
> Documentation has been compiled from git logs and by reading through
> code.
>
> Signed-off-by: Aishwarya Pant <aishpant@gmail.com>
> ---
> For drivers/block/loop.c, I don't see any maintainers or mailing lists except
> for LKML. I am guessing linux-block mailing list should be okay.
>
> Changes in v2:
> - Add linux-block@vger.kernel.org to the recipient list.
Applied to the docs tree, thanks.
jon
prev parent reply other threads:[~2018-02-23 15:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-17 6:13 [PATCH v2] block/loop: add documentation for sysfs interface Aishwarya Pant
2018-02-23 15:20 ` Jonathan Corbet [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=20180223082029.731acffd@lwn.net \
--to=corbet@lwn.net \
--cc=aishpant@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=julia.lawall@lip6.fr \
--cc=linux-block@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.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