devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh+dt@kernel.org>
To: Mans Rullgard <mans@mansr.com>
Cc: Pawel Moll <pawel.moll@arm.com>,
	Mark Rutland <mark.rutland@arm.com>,
	Ian Campbell <ijc+devicetree@hellion.org.uk>,
	Kumar Gala <galak@codeaurora.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/3] devicetree: add vendor prefix for Aurora VLSI
Date: Thu, 22 Oct 2015 09:35:36 -0500	[thread overview]
Message-ID: <CAL_JsqJkUEDoVf1n-X2kXsTVS5-ojO=deurSLcpuL_BQVAjDmQ@mail.gmail.com> (raw)
In-Reply-To: <1445522558-5808-1-git-send-email-mans@mansr.com>

On Thu, Oct 22, 2015 at 9:02 AM, Mans Rullgard <mans@mansr.com> wrote:
> This adds the vendor prefix "aurora" for Aurora VLSI, Inc.
>
> Signed-off-by: Mans Rullgard <mans@mansr.com>

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

> ---
>  Documentation/devicetree/bindings/vendor-prefixes.txt | 1 +
>  1 file changed, 1 insertion(+)
>
> diff --git a/Documentation/devicetree/bindings/vendor-prefixes.txt b/Documentation/devicetree/bindings/vendor-prefixes.txt
> index 82d2ac9..380ce10 100644
> --- a/Documentation/devicetree/bindings/vendor-prefixes.txt
> +++ b/Documentation/devicetree/bindings/vendor-prefixes.txt
> @@ -30,6 +30,7 @@ artesyn       Artesyn Embedded Technologies Inc.
>  asahi-kasei    Asahi Kasei Corp.
>  atmel  Atmel Corporation
>  auo    AU Optronics Corporation
> +aurora Aurora VLSI, Inc.
>  avago  Avago Technologies
>  avic   Shanghai AVIC Optoelectronics Co., Ltd.
>  axis   Axis Communications AB
> --
> 2.5.3
>

      parent reply	other threads:[~2015-10-22 14:35 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-22 14:02 [PATCH 1/3] devicetree: add vendor prefix for Aurora VLSI Mans Rullgard
2015-10-22 14:02 ` [PATCH 2/3] devicetree: add binding for Aurora VLSI NB8800 Ethernet controller Mans Rullgard
     [not found]   ` <1445522558-5808-2-git-send-email-mans-2StjZFpD7GcAvxtiuMwx3w@public.gmane.org>
2015-10-22 14:34     ` Rob Herring
2015-10-23 12:10   ` Marc Gonzalez
     [not found]     ` <562A23B9.3090208-y1yR0Z3OICC7zZZRDBGcUA@public.gmane.org>
2015-10-23 13:28       ` Rob Herring
2015-10-23 13:41       ` Måns Rullgård
2015-10-23 13:57         ` Marc Gonzalez
     [not found]           ` <562A3CD2.3050903-y1yR0Z3OICC7zZZRDBGcUA@public.gmane.org>
2015-10-23 14:06             ` Måns Rullgård
     [not found]         ` <yw1xio5xg0rq.fsf-OEaqT8BN2ezZK2NkWkPsZwC/G2K4zDHf@public.gmane.org>
2015-10-26  9:34           ` Marc Gonzalez
     [not found]             ` <562DF394.3030500-y1yR0Z3OICC7zZZRDBGcUA@public.gmane.org>
2015-10-26 12:05               ` Måns Rullgård
     [not found]                 ` <yw1x1tchg7i6.fsf-OEaqT8BN2ezZK2NkWkPsZwC/G2K4zDHf@public.gmane.org>
2015-10-26 13:28                   ` Marc Gonzalez
2015-10-26 13:54                     ` Måns Rullgård
2015-10-26 14:05                       ` Marc Gonzalez
2015-10-26 14:11                         ` Måns Rullgård
2015-10-22 14:35 ` Rob Herring [this message]

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='CAL_JsqJkUEDoVf1n-X2kXsTVS5-ojO=deurSLcpuL_BQVAjDmQ@mail.gmail.com' \
    --to=robh+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=galak@codeaurora.org \
    --cc=ijc+devicetree@hellion.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mans@mansr.com \
    --cc=mark.rutland@arm.com \
    --cc=pawel.moll@arm.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).