From: Rob Herring <robh@kernel.org>
To: Santiago Hormazabal <santiagohssl@gmail.com>
Cc: linux-media@vger.kernel.org, Hans Verkuil <hverkuil@xs4all.nl>,
devicetree@vger.kernel.org,
Ezequiel Garcia <ezequiel@collabora.com>,
Rob Herring <robh+dt@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] dt-bindings: vendor-prefixes: Add KT Micro
Date: Thu, 23 Jul 2020 14:51:00 -0600 [thread overview]
Message-ID: <20200723205100.GA837861@bogus> (raw)
In-Reply-To: <20200717004441.116248-2-santiagohssl@gmail.com>
On Thu, 16 Jul 2020 21:44:39 -0300, Santiago Hormazabal wrote:
> Adds ktm as the prefix of KT Micro, Inc.
>
> Signed-off-by: Santiago Hormazabal <santiagohssl@gmail.com>
> ---
> Documentation/devicetree/bindings/vendor-prefixes.yaml | 2 ++
> 1 file changed, 2 insertions(+)
>
Acked-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2020-07-23 20:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-17 0:44 [PATCH 0/3] KT091 FM/AM driver Santiago Hormazabal
2020-07-17 0:44 ` [PATCH 1/3] dt-bindings: vendor-prefixes: Add KT Micro Santiago Hormazabal
2020-07-23 20:51 ` Rob Herring [this message]
2020-07-17 0:44 ` [PATCH 2/3] media: kt0913: device tree binding Santiago Hormazabal
2020-07-23 20:51 ` Rob Herring
2020-07-17 0:44 ` [PATCH 3/3] media: Add support for the AM/FM radio chip KT0913 from KT Micro Santiago Hormazabal
2020-07-17 9:29 ` Hans Verkuil
2020-07-17 9:51 ` Joe Perches
2020-07-17 10:04 ` Hans Verkuil
2020-07-17 17:58 ` Joe Perches
2020-07-17 15:10 ` Santiago Hormazabal
2020-08-03 2:09 [PATCH 0/3] KT0913 FM/AM driver Santiago Hormazabal
2020-08-03 2:09 ` [PATCH 1/3] dt-bindings: vendor-prefixes: Add KT Micro Santiago Hormazabal
2020-08-03 13:00 ` Hans Verkuil
2020-08-31 22:05 [PATCH 0/3] KT0913 FM/AM driver Santiago Hormazabal
2020-08-31 22:05 ` [PATCH 1/3] dt-bindings: vendor-prefixes: Add KT Micro Santiago Hormazabal
2020-09-14 18:27 ` Rob Herring
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=20200723205100.GA837861@bogus \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=ezequiel@collabora.com \
--cc=hverkuil@xs4all.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=santiagohssl@gmail.com \
/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).