[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <AM9PR06MB78442036A5C52FCC5E248AD1D7379@AM9PR06MB7844.eurprd06.prod.outlook.com>
Date: Fri, 18 Feb 2022 05:34:48 +0000
From: LI Qingwu <qing-wu.li@...ca-geosystems.com.cn>
To: Rob Herring <robh@...nel.org>
CC: "robh+dt@...nel.org" <robh+dt@...nel.org>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
"linux-iio@...r.kernel.org" <linux-iio@...r.kernel.org>,
"jic23@...nel.org" <jic23@...nel.org>,
"tomas.melin@...sala.com" <tomas.melin@...sala.com>,
"andy.shevchenko@...il.com" <andy.shevchenko@...il.com>,
"lars@...afoo.de" <lars@...afoo.de>,
GEO-CHHER-bsp-development
<bsp-development.geo@...ca-geosystems.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH V2 1/5] dt-bindings: iio: accel: sca3300: Document
murata,scl3300
Hi Rob Herring
> -----Original Message-----
> From: Rob Herring <robh@...nel.org>
> Sent: Friday, February 18, 2022 7:04 AM
> To: LI Qingwu <qing-wu.li@...ca-geosystems.com.cn>
> Cc: robh+dt@...nel.org; devicetree@...r.kernel.org; linux-iio@...r.kernel.org;
> jic23@...nel.org; tomas.melin@...sala.com; andy.shevchenko@...il.com;
> lars@...afoo.de; GEO-CHHER-bsp-development
> <bsp-development.geo@...ca-geosystems.com>; linux-kernel@...r.kernel.org
> Subject: Re: [PATCH V2 1/5] dt-bindings: iio: accel: sca3300: Document
> murata,scl3300
>
> [Some people who received this message don't often get email from
> robh@...nel.org. Learn why this is important at
> http://aka.ms/LearnAboutSenderIdentification.]
>
> This email is not from Hexagon's Office 365 instance. Please be careful while
> clicking links, opening attachments, or replying to this email.
>
>
> On Thu, 17 Feb 2022 06:27:01 +0000, LI Qingwu wrote:
> > Add DT bindings for Murata scl3300 inclinometer.
> >
> > Signed-off-by: LI Qingwu <Qing-wu.Li@...ca-geosystems.com.cn>
> > ---
> > Documentation/devicetree/bindings/iio/accel/murata,sca3300.yaml | 1 +
> > 1 file changed, 1 insertion(+)
> >
>
>
> Please add Acked-by/Reviewed-by tags when posting new versions. However,.
> there's no need to repost patches *only* to add the tags. The upstream
> maintainer will do that for acks received on the version they apply.
>
> If a tag was not added on purpose, please state why and what changed.
Thanks, I will add in v3.
Powered by blists - more mailing lists