From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [PATCH v2] km: fix license string and compatible strings
Date: Thu, 8 Oct 2020 11:52:43 -0400 [thread overview]
Message-ID: <20201008155243.GD14816@bill-the-cat> (raw)
In-Reply-To: <20201008102722.19848-1-holger.brunck@hitachi-powergrids.com>
On Thu, Oct 08, 2020 at 12:27:22PM +0200, Holger Brunck wrote:
> As the ownership is now Hitachi Power Grids, change the license string
> and adapt the compatible string in DTS files. For kmeter1.dts we
> change it to "keymile,KMETER1" for now, as this is then compliant with
> what is submitted to the linux kernel. All other boards don't have
> a upstreamed version in linux mainline.
>
> Signed-off-by: Holger Brunck <holger.brunck@hitachi-powergrids.com>
> CC: Valentin Longchamp <valentin.longchamp@hitachi-powergrids.com>
> CC: Heiko Schocher <hs@denx.de>
> CC: Marek Vasut <marex@denx.de>
> CC: Tom Rini <trini@konsulko.com>
With the caveat that generally speaking these tags aren't supposed to
change, in order to keep compatibility, given that the changes are in
device trees not in the Linux kernel and thus also not apparently in use
in places where such compatibility is required (with the exception of
the one noted in the commit message):
Reviewed-by: Tom Rini <trini@konsulko.com>
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 659 bytes
Desc: not available
URL: <https://lists.denx.de/pipermail/u-boot/attachments/20201008/854061a3/attachment.sig>
next prev parent reply other threads:[~2020-10-08 15:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-08 10:27 [PATCH v2] km: fix license string and compatible strings Holger Brunck
2020-10-08 15:52 ` Tom Rini [this message]
2020-10-23 0:28 ` Tom Rini
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=20201008155243.GD14816@bill-the-cat \
--to=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/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