From: Dipen Patel <dipenp@nvidia•com>
To: Mark Brown <broonie@kernel•org>
Cc: linux-next@vger•kernel.org, linux-kernel@vger•kernel.org,
linux-arm-kernel@lists•infradead.org
Subject: Re: Missing signoffs in the hte tree
Date: Mon, 1 May 2023 12:40:16 -0700 [thread overview]
Message-ID: <14a6bbb9-aca7-750c-e004-2b11abf05926@nvidia.com> (raw)
In-Reply-To: <143a3e5b-ddc9-4ce1-88ea-9e4d80761cc1@sirena.org.uk>
On 4/24/23 5:07 AM, Mark Brown wrote:
> Commits
>
> 1af0f6b5060cf ("hte: tegra-194: Use proper includes")
> 3798a6e3b6a89 ("hte: Use device_match_of_node()")
> 981501927e482 ("hte: tegra-194: Fix off by one in tegra_hte_map_to_line_id()")
> 58e1189d075a4 ("hte: tegra: fix 'struct of_device_id' build error")
> 499c35fe9bf2e ("hte: Use of_property_present() for testing DT property presence")
>
> in the hte tree for today are missing a Signed-off-by from their
> committers.
Shouldn't Acked-by tag from me (maintainer of the HTE tree) enough? I mean it does imply signed-off-by, right?
next prev parent reply other threads:[~2023-05-01 19:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-24 12:07 Missing signoffs in the hte tree Mark Brown
2023-05-01 19:40 ` Dipen Patel [this message]
2023-05-02 0:03 ` Mark Brown
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=14a6bbb9-aca7-750c-e004-2b11abf05926@nvidia.com \
--to=dipenp@nvidia$(echo .)com \
--cc=broonie@kernel$(echo .)org \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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