From: Rob Herring <robh@kernel.org>
To: Rokosov Dmitry Dmitrievich <DDRokosov@sberdevices.ru>
Cc: "stano.jakubek@gmail.com" <stano.jakubek@gmail.com>,
"shawnguo@kernel.org" <shawnguo@kernel.org>,
"jic23@kernel.org" <jic23@kernel.org>,
"lars@metafoo.de" <lars@metafoo.de>,
"andy.shevchenko@gmail.com" <andy.shevchenko@gmail.com>,
"stephan@gerhold.net" <stephan@gerhold.net>,
"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
kernel <kernel@sberdevices.ru>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v1 1/3] dt-bindings: vendor-prefixes: add MEMSensing Microsystems Co., Ltd.
Date: Tue, 26 Apr 2022 15:28:03 -0500 [thread overview]
Message-ID: <YmhV08V2jTeB448O@robh.at.kernel.org> (raw)
In-Reply-To: <20220419154555.24191-2-ddrokosov@sberdevices.ru>
On Tue, Apr 19, 2022 at 03:45:51PM +0000, Rokosov Dmitry Dmitrievich 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(+)
>
> diff --git a/Documentation/devicetree/bindings/vendor-prefixes.yaml b/Documentation/devicetree/bindings/vendor-prefixes.yaml
> index 294093d..d8f29ad 100644
> --- a/Documentation/devicetree/bindings/vendor-prefixes.yaml
> +++ b/Documentation/devicetree/bindings/vendor-prefixes.yaml
> @@ -737,6 +737,8 @@ patternProperties:
> description: Mellanox Technologies
> "^memsic,.*":
> description: MEMSIC Inc.
> + "^memsensing,.*":
> + description: MEMSensing Microsystems Co., Ltd.
Alphabetical order. This needs to be before memsic.
> "^menlo,.*":
> description: Menlo Systems GmbH
> "^mentor,.*":
> --
> 2.9.5
>
next prev parent reply other threads:[~2022-04-26 20:28 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-19 15:45 [PATCH v1 0/3] iio: accel: add MSA311 accelerometer driver Rokosov Dmitry Dmitrievich
2022-04-19 15:45 ` [PATCH v1 1/3] dt-bindings: vendor-prefixes: add MEMSensing Microsystems Co., Ltd Rokosov Dmitry Dmitrievich
2022-04-26 20:28 ` Rob Herring [this message]
2022-04-27 9:01 ` Dmitry Rokosov
2022-04-19 15:45 ` [PATCH v1 2/3] iio: add MEMSensing MSA311 3-axis accelerometer driver Rokosov Dmitry Dmitrievich
2022-04-20 10:50 ` Jonathan Cameron
2022-04-26 17:23 ` Dmitry Rokosov
2022-04-28 19:41 ` Jonathan Cameron
2022-05-18 12:25 ` Dmitry Rokosov
2022-05-22 10:36 ` Jonathan Cameron
2022-05-25 17:53 ` Dmitry Rokosov
2022-04-20 10:54 ` Jonathan Cameron
2022-04-21 14:07 ` Dmitry Rokosov
2022-04-19 15:45 ` [PATCH v1 3/3] dt-bindings: iio: accel: add dt-binding schema for msa311 accel driver Rokosov Dmitry Dmitrievich
2022-04-20 8:51 ` Jonathan Cameron
2022-04-21 13:55 ` Dmitry Rokosov
2022-04-26 20:31 ` Rob Herring
2022-04-27 8:58 ` Dmitry Rokosov
2022-05-04 18:36 ` Dmitry Rokosov
2022-05-04 20:48 ` Jonathan Cameron
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=YmhV08V2jTeB448O@robh.at.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.