From: Soumya Negi <soumya.negi97@gmail.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Shuah Khan <skhan@linuxfoundation.org>,
Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
devicetree@vger.kernel.org,
linux-kernel-mentees@lists.linuxfoundation.org,
linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: mips: Convert plain text file to ReST
Date: Sat, 21 May 2022 12:55:59 -0700 [thread overview]
Message-ID: <20220521195558.GD14144@Negi> (raw)
In-Reply-To: <YojoMzjahyP+HW4m@kroah.com>
On Sat, May 21, 2022 at 03:25:07PM +0200, Greg KH wrote:
> On Fri, May 20, 2022 at 06:56:13PM -0700, Soumya Negi wrote:
> > Converts .txt documentation file to ReST format(.rst).
> >
> > Signed-off-by: Soumya Negi <soumya.negi97@gmail.com>
> > ---
> > .../devicetree/bindings/mips/cpu_irq.rst | 56 +++++++++++++++++++
> > 1 file changed, 56 insertions(+)
> > create mode 100644 Documentation/devicetree/bindings/mips/cpu_irq.rst
>
> That did not "convert" it merely added the new file. Where was the old
> file?
I will correct the patch. The old file is Documentation/devicetree/bindings/mips/cpu_irq.txt
> And does this get added to the build somehow?
No, I don't think so. When building documentation using make htmldocs, the file
does not show up in the Documentation/output directory.
Regards
Soumya
next prev parent reply other threads:[~2022-05-21 19:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-21 1:56 [PATCH] dt-bindings: mips: Convert plain text file to ReST Soumya Negi
2022-05-21 13:25 ` Greg KH
2022-05-21 19:55 ` Soumya Negi [this message]
2022-05-21 14:25 ` Krzysztof Kozlowski
2022-05-21 20:24 ` Soumya Negi
2022-05-22 7:51 ` Krzysztof Kozlowski
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=20220521195558.GD14144@Negi \
--to=soumya.negi97@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=tsbogend@alpha.franken.de \
/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).