devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Kamlesh Gurudasani <kamlesh.gurudasani@gmail.com>
Cc: noralf@tronnes.org, Sam Ravnborg <sam@ravnborg.org>,
	devicetree@vger.kernel.org, dri-devel@lists.freedesktop.org,
	Kamlesh Gurudasani <kamlesh.gurudasani@gmail.com>
Subject: Re: [PATCH v4 1/3] dt-bindings: add vendor prefix for OzzMaker and Waveshare Electronics
Date: Wed, 5 Feb 2020 17:33:09 +0000	[thread overview]
Message-ID: <20200205173309.GA2474@bogus> (raw)
In-Reply-To: <aa8799c4164b54fa5c4ca55e48966d7b61352c2c.1580134320.git.kamlesh.gurudasani@gmail.com>

On Mon, 27 Jan 2020 19:55:33 +0530, Kamlesh Gurudasani wrote:
> Add vendor prefix for OzzMaker [1] and Waveshare Electronics [2]
> Both are display manufacturers
> 
> [1] https://ozzmaker.com/about/
> [2] https://www.waveshare.com/contact_us
> 
> Signed-off-by: Kamlesh Gurudasani <kamlesh.gurudasani@gmail.com>
> ---
>  Documentation/devicetree/bindings/vendor-prefixes.yaml | 4 ++++
>  1 file changed, 4 insertions(+)
> 

Applied, thanks.

Rob

  parent reply	other threads:[~2020-02-05 17:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-27 14:24 [PATCH v4 0/3] Support for tft displays based on ilitek,ili9486 Kamlesh Gurudasani
2020-01-27 14:25 ` [PATCH v4 1/3] dt-bindings: add vendor prefix for OzzMaker and Waveshare Electronics Kamlesh Gurudasani
2020-01-29 19:48   ` Sam Ravnborg
2020-02-05 17:33   ` Rob Herring [this message]
2020-01-27 14:26 ` [PATCH v4 2/3] dt-bindings: add binding for tft displays based on ilitek,ili9486 Kamlesh Gurudasani
2020-01-29 20:14   ` Sam Ravnborg
2020-01-31 14:23   ` Rob Herring
2020-01-27 14:26 ` [PATCH v4 3/3] drm/tinydrm: add support " Kamlesh Gurudasani
2020-01-27 15:13   ` Noralf Trønnes
2020-01-29 20:15   ` Sam Ravnborg

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=20200205173309.GA2474@bogus \
    --to=robh@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=kamlesh.gurudasani@gmail.com \
    --cc=noralf@tronnes.org \
    --cc=sam@ravnborg.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;
as well as URLs for NNTP newsgroup(s).