From: Shawn Guo <shawnguo@kernel.org>
To: Andy Tang <andy.tang@nxp.com>
Cc: "mark.rutland@arm.com" <mark.rutland@arm.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Leo Li <leoyang.li@nxp.com>
Subject: Re: [EXT] Re: [PATCH] arm64: dts: ls1028a: fix a compatible issue
Date: Thu, 3 Oct 2019 16:44:47 +0800 [thread overview]
Message-ID: <20191003084443.GA22491@X250> (raw)
In-Reply-To: <VI1PR04MB4333F1CF5DF521678575D61EF3840@VI1PR04MB4333.eurprd04.prod.outlook.com>
On Tue, Sep 24, 2019 at 08:00:29AM +0000, Andy Tang wrote:
> Hi Shawn,
>
>
> > -----Original Message-----
> > From: Shawn Guo <shawnguo@kernel.org>
> > Sent: 2019年9月14日 10:43
> > To: Andy Tang <andy.tang@nxp.com>
> > Cc: Leo Li <leoyang.li@nxp.com>; robh+dt@kernel.org;
> > mark.rutland@arm.com; linux-arm-kernel@lists.infradead.org;
> > devicetree@vger.kernel.org
> > Subject: [EXT] Re: [PATCH] arm64: dts: ls1028a: fix a compatible issue
> >
> > Caution: EXT Email
> >
> > On Thu, Aug 29, 2019 at 03:34:39PM +0800, Yuantian Tang wrote:
> > > The I2C multiplexer used on ls1028aqds is PCA9547, not PCA9847.
> > > So correct it.
> >
> > Can elaborate the fix a little bit, saying what's the issue exactly with using
> > that incorrect compatible?
> Ok.
>
> >
> > >
> > > Signed-off-by: Yuantian Tang <andy.tang@nxp.com>
> >
> > Do we need a fix tag?
> What does "fix tag" mean?
Please search 'Fixes' in Documentation/process/submitting-patches.rst.
Shawn
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2019-10-03 8:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-29 7:34 [PATCH] arm64: dts: ls1028a: fix a compatible issue Yuantian Tang
2019-09-14 2:42 ` Shawn Guo
2019-09-24 8:00 ` [EXT] " Andy Tang
2019-10-03 8:44 ` Shawn Guo [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=20191003084443.GA22491@X250 \
--to=shawnguo@kernel.org \
--cc=andy.tang@nxp.com \
--cc=devicetree@vger.kernel.org \
--cc=leoyang.li@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@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