From: Shreeya Patel <shreeya.patel23498@gmail.com>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: skhan@linuxfoundation.org,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Viresh Kumar <viresh.kumar@linaro.org>,
Jonathan Corbet <corbet@lwn.net>,
Linux PM <linux-pm@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"open list:DOCUMENTATION" <linux-doc@vger.kernel.org>,
linux-kernel-mentees@lists.linuxfoundation.org
Subject: Re: [PATCH] Documentation: cpu-freq: Convert core.txt file to ReST format
Date: Sun, 07 Jul 2019 01:26:07 +0530 [thread overview]
Message-ID: <dcbc0088f31f26f80ab05e51787099df9b70262f.camel@gmail.com> (raw)
In-Reply-To: <CAJZ5v0hovK+BY0kozGvkyCgR5CFHpZUu71BZRjUUdCYV8fM5Hg@mail.gmail.com>
On Sat, 2019-07-06 at 09:58 +0200, Rafael J. Wysocki wrote:
> On Fri, Jul 5, 2019 at 11:04 PM Shreeya Patel
> <shreeya.patel23498@gmail.com> wrote:
> >
> > Convert core file to ReST format, in order to allow it to
> > be parsed by Sphinx. Make a minor change of correcting the wrong
> > function name cpufreq_put_cpu to cpufreq_cpu_put.
> > Also create an index.rst file in cpu-freq and add it's entry
> > in the main Documentation/index.rst file.
> >
> > Signed-off-by: Shreeya Patel <shreeya.patel23498@gmail.com>
>
> I've said "no" no three previous attempts and this one is not
> different.
>
Sorry, I was not knowing about it.
> I don't want to have anything .rst in Documentation/cpu-freq/.
>
> There is a *new* admin-guide doc for cpufreq already and what is
> missing is a *new* driver-api one.
>
Yes I saw that but it didn't include all the details given in
Documentation/cpu-freq hence I thought of sending this initial patch.
Thanks
> Thanks!
prev parent reply other threads:[~2019-07-06 19:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-05 21:04 [PATCH] Documentation: cpu-freq: Convert core.txt file to ReST format Shreeya Patel
2019-07-06 7:58 ` Rafael J. Wysocki
2019-07-06 19:56 ` Shreeya Patel [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=dcbc0088f31f26f80ab05e51787099df9b70262f.camel@gmail.com \
--to=shreeya.patel23498@gmail.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=rjw@rjwysocki.net \
--cc=skhan@linuxfoundation.org \
--cc=viresh.kumar@linaro.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