From: Rob Herring <robh@kernel.org>
To: Bitan Biswas <bbiswas@nvidia.com>
Cc: krzysztof.kozlowski@canonical.com, thierry.reding@gmail.com,
jonathanh@nvidia.com, rostedt@goodmis.org, mingo@redhat.com,
jassisinghbrar@gmail.com, p.zabel@pengutronix.de,
skomatineni@nvidia.com, broonie@kernel.org,
linus.walleij@linaro.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, linux-tegra@vger.kernel.org
Subject: Re: [PATCH V1 0/3] Add tegra header license and dt-bindings Copyright
Date: Thu, 23 Sep 2021 17:36:29 -0500 [thread overview]
Message-ID: <YU0Bbc4lqtENJ5WF@robh.at.kernel.org> (raw)
In-Reply-To: <20210921174434.4839-1-bbiswas@nvidia.com>
On Tue, Sep 21, 2021 at 10:44:31AM -0700, Bitan Biswas wrote:
> Few Tegra header file are missing license text.
> Some Tegra dt-bindings header do not have Copyright.
> Add license and Copyright for such Tegra header files.
Who do you expect to merge this? Tegra maintainers or I can apply
patches 1 and 3.
Series should be for 1 maintainer clearly, separate series per
maintainer if there's no dependencies (this case), or clearly state who
you think should take a series if it has cross tree dependencies.
Rob
next prev parent reply other threads:[~2021-09-23 22:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-21 17:44 [PATCH V1 0/3] Add tegra header license and dt-bindings Copyright Bitan Biswas
2021-09-21 17:44 ` [PATCH V1 1/3] dt-bindings: tegra: memory,bpmp-thermal: add SPDX license Bitan Biswas
2021-09-21 17:59 ` Krzysztof Kozlowski
2021-09-24 22:10 ` Bitan Biswas
2021-09-21 17:44 ` [PATCH V1 2/3] trace: events: tegra_apb_dma: add SPDX license identifier Bitan Biswas
2021-09-21 17:44 ` [PATCH V1 3/3] dt-bindings: tegra: clock,memory,thermal: add header Copyright Bitan Biswas
2021-09-24 7:42 ` Krzysztof Kozlowski
2021-09-24 21:51 ` Bitan Biswas
2021-09-23 22:36 ` Rob Herring [this message]
2021-09-24 7:40 ` [PATCH V1 0/3] Add tegra header license and dt-bindings Copyright Krzysztof Kozlowski
-- strict thread matches above, loose matches on Subject: below --
2021-09-21 11:27 Bitan Biswas
2021-09-21 9:42 Bitan Biswas
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=YU0Bbc4lqtENJ5WF@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=bbiswas@nvidia.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jassisinghbrar@gmail.com \
--cc=jonathanh@nvidia.com \
--cc=krzysztof.kozlowski@canonical.com \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=p.zabel@pengutronix.de \
--cc=rostedt@goodmis.org \
--cc=skomatineni@nvidia.com \
--cc=thierry.reding@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox