From: Thierry Reding <thierry.reding@gmail.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: Dipen Patel <dipenp@nvidia.com>,
jonathanh@nvidia.com, linux-kernel@vger.kernel.org,
linux-tegra@vger.kernel.org, linux-gpio@vger.kernel.org,
linus.walleij@linaro.org, devicetree@vger.kernel.org,
linux-doc@vger.kernel.org, robh+dt@kernel.org,
timestamp@lists.linux.dev, krzysztof.kozlowski+dt@linaro.org,
brgl@bgdev.pl, corbet@lwn.net, gregkh@linuxfoundation.org
Subject: Re: [V6 0/9] Add Tegra234 HTE support
Date: Fri, 14 Apr 2023 12:43:31 +0200 [thread overview]
Message-ID: <CA+PwDYeTkWp9vXMec99H2OKOGhx0mOrnthT08=JkMkEsi4NDPw@mail.gmail.com> (raw)
In-Reply-To: <373eacb8-be3f-6b95-3e08-f0ff36f79891@linaro.org>
On Fri, Apr 14, 2023 at 09:36:15AM +0200, Krzysztof Kozlowski wrote:
> On 14/04/2023 02:44, Dipen Patel wrote:
> > This patch series mainly adds support for the Tegra234 HTE provider. In
> > addition, it addresses dt binding comments which prompted code
> > changes in the existing HTE provider driver without breaking the
> > Tegra194 provider. The comments raised concern how existing code
> > retrieves gpio controller node
> > (the node is used to help namespace conversion between HTE and GPIOLIB).
> > To help simplify that process, new DT property is suggested which adds
> > gpio controller node in the HTE provider binding as phandle property. To
> > conlude this patch series:
> > - adds Tegra234 HTE provider
> > - modifies existing provider code to address new dt binding for Tegra234
> > without breaking it for the Tegra194 chip.
> >
> > The V1 patch series:
> > - Adds tegra Tegra234 HTE(timestamp) provider supports.
> > - Updates MAINTAINERS file for git tree, mail list fields.
> > - Updates devicetree and API documentations.
> > - Enables HTE subsystem, Tegra194 and Tegra234 HTE providers
> > by default in arm64 defconfig and dts files.
>
> All your emails miss PATCH prefix. Use `git format-patch` to generate
> proper versioned patch. Stripping important part messes up with our
> filters. We have quite a lot of emails, so proper filtering is important.
I used to get this wrong as well because I didn't know (or perhaps it
didn't exist yet at the time) --reroll-count|-v and used to manually
override --subject-prefix.
Thierry
next prev parent reply other threads:[~2023-04-14 10:43 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-14 0:44 [V6 0/9] Add Tegra234 HTE support Dipen Patel
2023-04-14 0:44 ` [V6 1/9] MAINTAINERS: Add HTE/timestamp subsystem details Dipen Patel
2023-04-14 0:44 ` [V6 2/9] dt-bindings: timestamp: Add Tegra234 support Dipen Patel
2023-04-14 0:44 ` [V6 3/9] dt-bindings: timestamp: Deprecate nvidia,slices property Dipen Patel
2023-04-14 0:44 ` [V6 4/9] arm64: tegra: Add Tegra234 GTE nodes Dipen Patel
2023-04-20 16:05 ` Thierry Reding
2023-04-14 0:44 ` [V6 5/9] hte: Re-phrase tegra API document Dipen Patel
2023-04-14 0:44 ` [V6 6/9] hte: Add Tegra234 provider Dipen Patel
2023-04-14 0:44 ` [V6 7/9] hte: Deprecate nvidia,slices property Dipen Patel
2023-04-14 0:44 ` [V6 8/9] hte: handle nvidia,gpio-controller property Dipen Patel
2023-04-14 0:44 ` [V6 9/9] gpio: tegra186: Add Tegra234 hte support Dipen Patel
2023-04-14 7:36 ` [V6 0/9] Add Tegra234 HTE support Krzysztof Kozlowski
2023-04-14 8:07 ` Linus Walleij
2023-04-14 17:15 ` Dipen Patel
2023-04-14 10:43 ` Thierry Reding [this message]
2023-04-14 17:14 ` Dipen Patel
2023-04-14 20:47 ` 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='CA+PwDYeTkWp9vXMec99H2OKOGhx0mOrnthT08=JkMkEsi4NDPw@mail.gmail.com' \
--to=thierry.reding@gmail.com \
--cc=brgl@bgdev.pl \
--cc=corbet@lwn.net \
--cc=devicetree@vger.kernel.org \
--cc=dipenp@nvidia.com \
--cc=gregkh@linuxfoundation.org \
--cc=jonathanh@nvidia.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--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=timestamp@lists.linux.dev \
/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.