devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Harigovindan P <harigovi@codeaurora.org>
Cc: dri-devel@lists.freedesktop.org, linux-arm-msm@vger.kernel.org,
	freedreno@lists.freedesktop.org, devicetree@vger.kernel.org,
	sean@poorly.run, seanpaul@chromium.org,
	Harigovindan P <harigovi@codeaurora.org>
Subject: Re: [PATCH v12 2/2] dt-bindings: documenting compatible string vendor  "visionox"
Date: Tue, 5 May 2020 10:40:29 -0500	[thread overview]
Message-ID: <20200505154029.GA4222@bogus> (raw)
In-Reply-To: <20200429054515.4976-2-harigovi@codeaurora.org>

On Wed, 29 Apr 2020 11:15:15 +0530, Harigovindan P wrote:
> Documenting compatible string vendor "visionox" in vendor-prefix yaml file.
> 
> Signed-off-by: Harigovindan P <harigovi@codeaurora.org>
> ---
> Changes in v11:
> 	- Added compatible string in vendor-prefix yaml file
> 
> Changes in v12:
> 	- Fixed the string to clear dt_binding_check errors.
> 
>  Documentation/devicetree/bindings/vendor-prefixes.yaml | 2 ++
>  1 file changed, 2 insertions(+)
> 

Acked-by: Rob Herring <robh@kernel.org>

  reply	other threads:[~2020-05-05 15:40 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-21  4:55 [PATCH v11 0/2] Add support for rm69299 Visionox panel driver and add devicetree bindings for visionox panel Harigovindan P
2020-04-21  4:55 ` [PATCH v11 1/2] drm/panel: add support for rm69299 visionox panel driver Harigovindan P
2020-04-21 20:00   ` Matthias Kaehlcke
2020-05-06 18:57   ` Sam Ravnborg
2020-05-14  3:35     ` Dave Airlie
2020-05-14  4:43       ` Sam Ravnborg
2020-04-21  4:55 ` [PATCH v11 2/2] dt-bindings: documenting compatible string vendor "visionox" Harigovindan P
2020-04-22 19:40   ` Rob Herring
2020-04-29  5:45 ` [PATCH v12 " Harigovindan P
2020-05-05 15:40   ` Rob Herring [this message]
2020-05-06 18:56   ` 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=20200505154029.GA4222@bogus \
    --to=robh@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=freedreno@lists.freedesktop.org \
    --cc=harigovi@codeaurora.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=sean@poorly.run \
    --cc=seanpaul@chromium.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).