From: Ying Liu <victor.liu@nxp.com>
To: Alexander Stein <alexander.stein@ew.tq-group.com>,
Vinod Koul <vkoul@kernel.org>,
Kishon Vijay Abraham I <kishon@kernel.org>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>
Cc: Pengutronix Kernel Team <kernel@pengutronix.de>,
dl-linux-imx <linux-imx@nxp.com>,
"linux-phy@lists.infradead.org" <linux-phy@lists.infradead.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: RE: [PATCH 1/1] phy: freescale: phy-fsl-imx8-mipi-dphy: Fix alias name to use dashes
Date: Wed, 20 Dec 2023 02:27:13 +0000 [thread overview]
Message-ID: <AM7PR04MB70468E3BDB14C528F8F3654C9896A@AM7PR04MB7046.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <20231219090248.3317500-1-alexander.stein@ew.tq-group.com>
On Tuesday, December 19, 2023 5:03 PM, Alexander Stein <alexander.stein@ew.tq-group.com> wrote:
> Devicetree spec lists only dashes as valid characters for alias names.
This saying is not accurate because it lists digit, lowercase letter and
dash characters.
> Table 3.2: Valid characters for alias names, Devicee Specification,
> Release v0.4
>
> Signed-off-by: Alexander Stein <alexander.stein@ew.tq-group.com>
It makes sense to add a Fixes tag:
Fixes: 3fbae284887d ("phy: freescale: phy-fsl-imx8-mipi-dphy: Add i.MX8qxp LVDS PHY mode support")
Regards,
Liu Ying
--
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy
prev parent reply other threads:[~2023-12-20 2:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-19 9:02 [PATCH 1/1] phy: freescale: phy-fsl-imx8-mipi-dphy: Fix alias name to use dashes Alexander Stein
2023-12-19 9:09 ` Andrew Lunn
2023-12-19 9:13 ` Alexander Stein
2023-12-19 11:59 ` Vladimir Oltean
2023-12-20 2:27 ` Ying Liu [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=AM7PR04MB70468E3BDB14C528F8F3654C9896A@AM7PR04MB7046.eurprd04.prod.outlook.com \
--to=victor.liu@nxp.com \
--cc=alexander.stein@ew.tq-group.com \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=kishon@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-phy@lists.infradead.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=vkoul@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).