linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: lxsameer@gnu.org, corbet@lwn.net
Cc: linux-doc@vger.kernel.org
Subject: Re: [PATCH] Documentation: kobject.txt has been reviewed and converted to rst
Date: Tue, 18 Feb 2020 15:58:14 -0800	[thread overview]
Message-ID: <4f1e8771-1902-885f-63e2-bb8d37dc5a91@infradead.org> (raw)
In-Reply-To: <20200218213815.60856-1-lxsameer@gnu.org>

On 2/18/20 1:38 PM, lxsameer@gnu.org wrote:
> From: Sameer Rahmani <lxsameer@gnu.org>
> 
> Reivew the `kobject.txt` file and moved the converted rst version to `core-api`
> section where it makes more sense.
> 
> Signed-off-by: Sameer Rahmani <lxsameer@gnu.org>
> ---
>  Documentation/core-api/index.rst   |   1 +
>  Documentation/core-api/kobject.rst | 434 +++++++++++++++++++++++++++++
>  2 files changed, 435 insertions(+)
>  create mode 100644 Documentation/core-api/kobject.rst

> diff --git a/Documentation/core-api/kobject.rst b/Documentation/core-api/kobject.rst
> new file mode 100644
> index 000000000000..42f47ee36b63
> --- /dev/null
> +++ b/Documentation/core-api/kobject.rst
> @@ -0,0 +1,434 @@

Hi,
Did you make any non-Sphinx-format changes to kobject.txt {or .rst}?
It's difficult to tell in this patch format.
If you are making any changes to koject.txt, please do that in a
separate patch so that we can review it, then do the conversion from
.txt to .rst.  You also need to remove the kobject.txt file.


thanks.
-- 
~Randy


      reply	other threads:[~2020-02-18 23:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-18 21:38 [PATCH] Documentation: kobject.txt has been reviewed and converted to rst lxsameer
2020-02-18 23:58 ` Randy Dunlap [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=4f1e8771-1902-885f-63e2-bb8d37dc5a91@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=lxsameer@gnu.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;
as well as URLs for NNTP newsgroup(s).