Linux Kernel Mentees list
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Pragat Pandya <pragat.pandya@gmail.com>
Cc: linux-kernel-mentees@lists.linuxfoundation.org,
	linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [Linux-kernel-mentees] [PATCH v2 0/2] Documentation: Add files to driver-api manual
Date: Mon, 2 Mar 2020 11:43:00 -0700	[thread overview]
Message-ID: <20200302114300.34875f69@lwn.net> (raw)
In-Reply-To: <20200302183105.27628-1-pragat.pandya@gmail.com>

On Tue,  3 Mar 2020 00:01:03 +0530
Pragat Pandya <pragat.pandya@gmail.com> wrote:

> This patchset adds following two rst files under
> Documentation/driver-api and references these both in Sphinx TOC Tree in
> Documentation/driver-api/index.rst
>  -io-mapping.rst
>  -io_ordering.rst
> 
> v2: 
>  -Provide more descriptive subject lines
>  -The document did not belong to top level so moved it to driver-api
>   manual
> 
> Pragat Pandya (2):
>   Documentation: Add io-mapping.rst to driver-api manual
>   Documentation: Add io_ordering.rst to driver-api manual
> 
>  Documentation/driver-api/index.rst       |  2 +
>  Documentation/driver-api/io-mapping.rst  | 97 ++++++++++++++++++++++++
>  Documentation/driver-api/io_ordering.rst | 51 +++++++++++++
>  3 files changed, 150 insertions(+)
>  create mode 100644 Documentation/driver-api/io-mapping.rst
>  create mode 100644 Documentation/driver-api/io_ordering.rst

OK, we're getting closer.  This series, though, leaves the old files in
place.  You should rename them over, rather than simply creating new files.

Thanks,

jon
_______________________________________________
Linux-kernel-mentees mailing list
Linux-kernel-mentees@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/linux-kernel-mentees

  parent reply	other threads:[~2020-03-02 18:43 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-02 17:39 [Linux-kernel-mentees] [PATCH 0/2] Documentation: Add two new rst files Pragat Pandya
2020-03-02 17:39 ` [Linux-kernel-mentees] [PATCH 1/2] Documentation: Add a new .rst file under Documentation Pragat Pandya
2020-03-02 17:45   ` Jonathan Corbet
2020-03-02 18:31     ` [Linux-kernel-mentees] [PATCH v2 0/2] Documentation: Add files to driver-api manual Pragat Pandya
2020-03-02 18:31       ` [Linux-kernel-mentees] [PATCH v2 1/2] Documentation: Add io-mapping.rst " Pragat Pandya
2020-03-02 18:31       ` [Linux-kernel-mentees] [PATCH v2 2/2] Documentation: Add io_ordering.rst " Pragat Pandya
2020-03-02 18:43       ` Jonathan Corbet [this message]
2020-03-03  5:02         ` [Linux-kernel-mentees] [PATCH v3 0/2] Documentation: Rename two txt files to rst Pragat Pandya
2020-03-03  5:03           ` [Linux-kernel-mentees] [PATCH v3 1/2] Documentation: Add io-mapping.rst to driver-api manual Pragat Pandya
2020-03-03  5:03           ` [Linux-kernel-mentees] [PATCH v3 2/2] Documentation: Add io_ordering.rst " Pragat Pandya
2020-03-10 17:34           ` [Linux-kernel-mentees] [PATCH v3 0/2] Documentation: Rename two txt files to rst Jonathan Corbet
2020-03-02 17:39 ` [Linux-kernel-mentees] [PATCH 2/2] Documentation: Add a new .rst file under Documentation Pragat Pandya

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=20200302114300.34875f69@lwn.net \
    --to=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel-mentees@lists.linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pragat.pandya@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