From: Dipen Patel <dipenp@nvidia.com>
To: teng sterling <sterlingteng@gmail.com>
Cc: <smangipudi@nvidia.com>, <thierry.reding@gmail.com>,
<jonathanh@nvidia.com>, <linux-kernel@vger.kernel.org>,
<linux-tegra@vger.kernel.org>, <linux-gpio@vger.kernel.org>,
<linus.walleij@linaro.org>, <bgolaszewski@baylibre.com>,
<warthog618@gmail.com>, <devicetree@vger.kernel.org>,
Linux Doc Mailing List <linux-doc@vger.kernel.org>,
<robh+dt@kernel.org>
Subject: Re: [RFC v4 01/11] Documentation: Add HTE subsystem guide
Date: Wed, 19 Jan 2022 20:25:05 -0800 [thread overview]
Message-ID: <7c8a32fd-8233-cc69-d4d3-668a3a14aa14@nvidia.com> (raw)
In-Reply-To: <CAMU9jJoFAG4taoN0SSbVGPFMKyUnkT9VkrtatGuRpU-ek+hJ2g@mail.gmail.com>
Hi Teng,
I believe I added in patch 0003. Before sending this patch series, I did make htmldocs and did compile successfully. Let me know in case I am missing something.
On 1/19/22 6:03 PM, teng sterling wrote:
> Dipen Patel <dipenp@nvidia.com> 于2022年1月18日周二 11:06写道：
>> Adding hte document which can help understand various APIs implemented
>> in HTE framework for the HTE producers and the consumers.
>>
>> Signed-off-by: Dipen Patel <dipenp@nvidia.com>
>> ---
>> Changes in v2:
>> - Removed explanation, instead added kernel-doc references.
>>
>> Changes in v3:
>> - Addressed grammatical errors.
>>
>> Changes in v4:
>> - Added new API hte_req_ts_by_linedata_ns description.
>> - Removed hte_req_ts_by_hte_name.
>>
>> Documentation/hte/hte.rst | 83 +++++++++++++++++++++++++++++++++++++++
> Hi Dipen
>
> A document build warning will be introduced，Need to add it to the index:
>
> 1) Create Documentation/hte/index.rst
> 2) Add hte/index.rst into Documentation/index.rst
> 3) Add hte.rst into Documentation/hte/index.rst
>
> Thanks,
> Yanteng
next prev parent reply other threads:[~2022-01-20 4:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-18 0:22 [RFC v4 00/11] Intro to Hardware timestamping engine Dipen Patel
2022-01-18 0:22 ` [RFC v4 01/11] Documentation: Add HTE subsystem guide Dipen Patel
2022-01-20 2:03 ` teng sterling
2022-01-20 4:25 ` Dipen Patel [this message]
2022-01-22 2:22 ` teng sterling
2022-01-18 0:22 ` [RFC v4 02/11] drivers: Add hardware timestamp engine (HTE) Dipen Patel
2022-01-18 0:22 ` [RFC v4 03/11] hte: Add tegra194 HTE kernel provider Dipen Patel
2022-01-18 0:22 ` [RFC v4 04/11] dt-bindings: Add HTE bindings Dipen Patel
2022-01-18 0:22 ` [RFC v4 05/11] hte: Add Tegra194 IRQ HTE test driver Dipen Patel
2022-01-18 0:22 ` [RFC v4 06/11] gpiolib: Add HTE support Dipen Patel
2022-01-18 0:22 ` [RFC v4 07/11] gpio: tegra186: Add HTE in gpio-tegra186 driver Dipen Patel
2022-01-18 0:22 ` [RFC v4 08/11] gpiolib: cdev: Add hardware timestamp clock type Dipen Patel
2022-01-18 0:22 ` [RFC v4 09/11] tools: gpio: Add new hardware " Dipen Patel
2022-01-18 0:22 ` [RFC v4 10/11] hte: Add tegra GPIO HTE test driver Dipen Patel
2022-01-18 0:22 ` [RFC v4 11/11] MAINTAINERS: Added HTE Subsystem Dipen Patel
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=7c8a32fd-8233-cc69-d4d3-668a3a14aa14@nvidia.com \
--to=dipenp@nvidia.com \
--cc=bgolaszewski@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=jonathanh@nvidia.com \
--cc=linus.walleij@linaro.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=smangipudi@nvidia.com \
--cc=sterlingteng@gmail.com \
--cc=thierry.reding@gmail.com \
--cc=warthog618@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.