From: Nishanth Menon <nm@ti.com>
To: <peda@axentia.se>, Roger Quadros <rogerq@ti.com>
Cc: Nishanth Menon <nm@ti.com>, <t-kristo@ti.com>, <nsekhar@ti.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <devicetree@vger.kernel.org>,
<robh+dt@kernel.org>, <kishon@ti.com>
Subject: Re: [PATCH v2] arm64: dts: ti: k3-j721e: Rename mux header and update macro names
Date: Mon, 21 Sep 2020 07:33:07 -0500 [thread overview]
Message-ID: <160069143453.25898.17991361187968273734.b4-ty@ti.com> (raw)
In-Reply-To: <20200918165930.2031-1-rogerq@ti.com>
On Fri, 18 Sep 2020 19:59:30 +0300, Roger Quadros wrote:
> We intend to use one header file for SERDES MUX for all
> TI SoCs so rename the header file.
>
> The exsting macros are too generic. Prefix them with SoC name.
>
> While at that, add the missing configurations for completeness.
Hi Roger Quadros,
I have applied the following to branch for-5.9-dts on [1].
Thank you!
[1/1] arm64: dts: ti: k3-j721e: Rename mux header and update macro names
commit: c65176fd49f45bd5a5ffaa1790109745d1fa462c
I have also applied ti-k3-dt-fixes-for-v5.9 tag which I will be sending
for 5.9 in the next few mins.
You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.
If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.
Please add any relevant lists and maintainers to the CCs when replying
to this mail.
[1] git://git.kernel.org/pub/scm/linux/kernel/git/nmenon/linux.git
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
prev parent reply other threads:[~2020-09-21 12:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-18 16:59 [PATCH v2] arm64: dts: ti: k3-j721e: Rename mux header and update macro names Roger Quadros
2020-09-21 12:33 ` Nishanth Menon [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=160069143453.25898.17991361187968273734.b4-ty@ti.com \
--to=nm@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=kishon@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nsekhar@ti.com \
--cc=peda@axentia.se \
--cc=robh+dt@kernel.org \
--cc=rogerq@ti.com \
--cc=t-kristo@ti.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;
as well as URLs for NNTP newsgroup(s).