From: khilman@baylibre.com (Kevin Hilman)
To: linus-amlogic@lists.infradead.org
Subject: [PATCH 1/2] devicetree: Add vendor prefix for Hwacom Systems Inc.
Date: Sun, 26 Feb 2017 13:45:56 -0800 [thread overview]
Message-ID: <m2mvd839t7.fsf@baylibre.com> (raw)
In-Reply-To: <20170222142558.wbedfw6l4maatkdy@rob-hp-laptop> (Rob Herring's message of "Wed, 22 Feb 2017 08:25:58 -0600")
Rob Herring <robh@kernel.org> writes:
> On Sun, Feb 12, 2017 at 08:32:46PM +0100, Carlo Caione wrote:
>> From: Carlo Caione <carlo@endlessm.com>
>>
>> Hwacom Systems Inc. is a broadband system integrator and supplier of
>> mobile, fixed and IP networks related services as well as
>> multimedia application. Website: http://www.hwacom.com/
>>
>> Signed-off-by: Carlo Caione <carlo@endlessm.com>
>> ---
>> Documentation/devicetree/bindings/vendor-prefixes.txt | 1 +
>> 1 file changed, 1 insertion(+)
>
> Acked-by: Rob Herring <robh@kernel.org>
Rob, I assume I should take this patch along with the patch that's using
this prefix? Or does this go through some other DT path?
Kevin
next prev parent reply other threads:[~2017-02-26 21:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-12 19:32 [PATCH 0/2] Add support for HwaCom AmazeTV Carlo Caione
2017-02-12 19:32 ` [PATCH 1/2] devicetree: Add vendor prefix for Hwacom Systems Inc Carlo Caione
2017-02-22 14:25 ` Rob Herring
2017-02-26 21:45 ` Kevin Hilman [this message]
2017-02-27 13:29 ` Rob Herring
2017-02-27 19:02 ` Andreas Färber
2017-02-27 22:18 ` Rob Herring
2017-02-12 19:32 ` [PATCH 2/2] ARM64: dts: meson-gxl: Add support for HwaCom AmazeTV Carlo Caione
2017-02-22 14:44 ` Rob Herring
2017-02-22 14:47 ` Carlo Caione
2017-02-22 14:49 ` Andreas Färber
2017-02-22 17:41 ` Rob Herring
2017-02-22 16:31 [PATCH 0/2] " Carlo Caione
2017-02-22 16:31 ` [PATCH 1/2] devicetree: Add vendor prefix for Hwacom Systems Inc Carlo Caione
2017-03-03 18:57 ` Kevin Hilman
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=m2mvd839t7.fsf@baylibre.com \
--to=khilman@baylibre.com \
--cc=linus-amlogic@lists.infradead.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
all inboxes | Powered by JetHome®