From: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
To: "Peng Fan (OSS)" <peng.fan@oss.nxp.com>,
jassisinghbrar@gmail.com, robh+dt@kernel.org,
shawnguo@kernel.org
Cc: s.hauer@pengutronix.de, kernel@pengutronix.de,
festevam@gmail.com, linux-imx@nxp.com,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, Peng Fan <peng.fan@nxp.com>
Subject: Re: [PATCH 5/5] mailbox: imx: update author and Copyright
Date: Mon, 7 Feb 2022 21:07:06 +0100 [thread overview]
Message-ID: <9bb00b0c-6d5d-3dc3-776b-6ecce0268407@canonical.com> (raw)
In-Reply-To: <20220207095832.1590225-6-peng.fan@oss.nxp.com>
On 07/02/2022 10:58, Peng Fan (OSS) wrote:
> From: Peng Fan <peng.fan@nxp.com>
>
> Add NXP Copyright
> Add myself as author
>
> Signed-off-by: Peng Fan <peng.fan@nxp.com>
> ---
> drivers/mailbox/imx-mailbox.c | 2 ++
> 1 file changed, 2 insertions(+)
>
Just squash it with previous update. Usually the copyright is updated
because of introduced work, so keeping it a separate commit does not
make much sense.
Best regards,
Krzysztof
prev parent reply other threads:[~2022-02-07 20:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-07 9:58 [PATCH 0/5] mailbox: imx: support i.MX93 Peng Fan (OSS)
2022-02-07 9:58 ` [PATCH 1/5] dt-bindings: mailbox: imx-mu: add i.MX93 MU Peng Fan (OSS)
2022-02-07 19:59 ` Krzysztof Kozlowski
2022-02-07 9:58 ` [PATCH 2/5] dt-bindings: mailbox: imx-mu: add i.MX93 S4 MU support Peng Fan (OSS)
2022-02-07 20:05 ` Krzysztof Kozlowski
2022-02-07 9:58 ` [PATCH 3/5] mailbox: imx: extend irq to an array Peng Fan (OSS)
2022-02-07 9:58 ` [PATCH 4/5] mailbox: imx: support i.MX93 S401 MU Peng Fan (OSS)
2022-02-07 9:58 ` [PATCH 5/5] mailbox: imx: update author and Copyright Peng Fan (OSS)
2022-02-07 20:07 ` Krzysztof Kozlowski [this message]
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=9bb00b0c-6d5d-3dc3-776b-6ecce0268407@canonical.com \
--to=krzysztof.kozlowski@canonical.com \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=jassisinghbrar@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peng.fan@nxp.com \
--cc=peng.fan@oss.nxp.com \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
/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
all inboxes | Powered by JetHome®