From: Rob Herring <robh@kernel.org>
To: Dmitry Rokosov <DDRokosov@sberdevices.ru>
Cc: "andy.shevchenko@gmail.com" <andy.shevchenko@gmail.com>,
kernel <kernel@sberdevices.ru>,
"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
"stano.jakubek@gmail.com" <stano.jakubek@gmail.com>,
"shawnguo@kernel.org" <shawnguo@kernel.org>,
"stephan@gerhold.net" <stephan@gerhold.net>,
"lars@metafoo.de" <lars@metafoo.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"jic23@kernel.org" <jic23@kernel.org>
Subject: Re: [PATCH v2 1/3] dt-bindings: vendor-prefixes: add MEMSensing Microsystems Co., Ltd.
Date: Thu, 2 Jun 2022 10:50:10 -0500 [thread overview]
Message-ID: <20220602155010.GA2349024-robh@kernel.org> (raw)
In-Reply-To: <20220602135934.f4exakny4rbrdboy@CAB-WSD-L081021.sigma.sbrf.ru>
On Thu, Jun 02, 2022 at 01:59:18PM +0000, Dmitry Rokosov wrote:
> Rob,
>
> Thank you for the Ack. I'm going to send v3 patch series and don't
> understand, should I append Acked-by line to v3 version of vendor-prefix
> patch... Please suggest me if possible.
Yes. When you send another version, add any acks unless there are
significant changes that warrant not adding them. You don't need to send
another version just to add acks. The maintainer will add any given on
the current version.
Rob
>
> On Thu, Jun 02, 2022 at 08:50:15AM -0500, Rob Herring wrote:
> > On Wed, 25 May 2022 18:15:30 +0000, Dmitry Rokosov wrote:
> > > MEMSensing Microsystems (Suzhou, China) Co., Ltd. operates as a micro
> > > electromechanical system technology company which produces micro
> > > electromechanical system microphones and sensors.
> > > MEMSensing Microsystems (Suzhou, China) Co., Ltd. applies its products
> > > in consumer electronics, industrial control, medical electronics
> > > and automotive, and other fields.
> > >
> > > Signed-off-by: Dmitry Rokosov <ddrokosov@sberdevices.ru>
> > > ---
> > > Documentation/devicetree/bindings/vendor-prefixes.yaml | 2 ++
> > > 1 file changed, 2 insertions(+)
> > >
> >
> > Acked-by: Rob Herring <robh@kernel.org>
>
> --
> Thank you,
> Dmitry
next prev parent reply other threads:[~2022-06-02 15:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-25 18:15 [PATCH v2 0/3] iio: accel: add MSA311 accelerometer driver Dmitry Rokosov
2022-05-25 18:15 ` [PATCH v2 1/3] dt-bindings: vendor-prefixes: add MEMSensing Microsystems Co., Ltd Dmitry Rokosov
2022-06-02 13:50 ` Rob Herring
2022-06-02 13:59 ` Dmitry Rokosov
2022-06-02 15:50 ` Rob Herring [this message]
2022-05-25 18:15 ` [PATCH v2 2/3] iio: add MEMSensing MSA311 3-axis accelerometer driver Dmitry Rokosov
2022-05-28 18:33 ` Jonathan Cameron
2022-06-09 18:09 ` Dmitry Rokosov
2022-06-12 9:02 ` Jonathan Cameron
2022-06-12 9:46 ` Christophe JAILLET
2022-06-12 12:51 ` Dmitry Rokosov
2022-05-25 18:15 ` [PATCH v2 3/3] dt-bindings: iio: accel: add dt-binding schema for msa311 accel driver Dmitry Rokosov
2022-05-25 18:32 ` Dmitry Rokosov
2022-05-28 17:43 ` Jonathan Cameron
2022-06-02 17:39 ` Dmitry Rokosov
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=20220602155010.GA2349024-robh@kernel.org \
--to=robh@kernel.org \
--cc=DDRokosov@sberdevices.ru \
--cc=andy.shevchenko@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=jic23@kernel.org \
--cc=kernel@sberdevices.ru \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shawnguo@kernel.org \
--cc=stano.jakubek@gmail.com \
--cc=stephan@gerhold.net \
/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).