From: Dipen Patel <dipenp@nvidia.com>
To: Linus Walleij <linus.walleij@linaro.org>,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: thierry.reding@gmail.com, jonathanh@nvidia.com,
linux-kernel@vger.kernel.org, linux-tegra@vger.kernel.org,
linux-gpio@vger.kernel.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,
Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Subject: Re: [V6 0/9] Add Tegra234 HTE support
Date: Fri, 14 Apr 2023 10:15:48 -0700 [thread overview]
Message-ID: <4b5e45e9-6aa8-7338-acc4-db06ca1fe025@nvidia.com> (raw)
In-Reply-To: <CACRpkdY6R9WvwOr3mVgrJcf9dVB4s13eu8juZkBt0Q+=gg2G2w@mail.gmail.com>
On 4/14/23 1:07 AM, Linus Walleij wrote:
> On Fri, Apr 14, 2023 at 9:36 AM Krzysztof Kozlowski
> <krzysztof.kozlowski@linaro.org> 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.
>
> At this point I would even recommend kernel maintainers to get b4
> into the workflow:
> https://people.kernel.org/monsieuricon/sending-a-kernel-patch-with-b4-part-1
Thanks for sharing...will have to look into it to avoid such mistakes.
>
> This tool will also implement other desired behaviours and version
> the patch set for you.
>
> I am gradually adopting it for my own work, using it all the time when
> applying patches but also getting better at using it for submitting
> them. It has a small overhead (like learning and memorizing the
> subcommands) but once you get used to it, it is really helpful.
>
> Yours,
> Linus Walleij
next prev parent reply other threads:[~2023-04-14 17:15 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 [this message]
2023-04-14 10:43 ` Thierry Reding
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=4b5e45e9-6aa8-7338-acc4-db06ca1fe025@nvidia.com \
--to=dipenp@nvidia.com \
--cc=brgl@bgdev.pl \
--cc=corbet@lwn.net \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jonathanh@nvidia.com \
--cc=konstantin@linuxfoundation.org \
--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=thierry.reding@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox