All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Rob Herring <robh@kernel.org>
Cc: Nikita Travkin <nikita@trvn.ru>,
	lars@metafoo.de, linux-iio@vger.kernel.org, robh+dt@kernel.org,
	stephan@gerhold.net, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/4] dt-bindings: vendor-prefixes: Document liteon vendor prefix
Date: Sat, 16 Oct 2021 16:55:52 +0100	[thread overview]
Message-ID: <20211016165552.680b2438@jic23-huawei> (raw)
In-Reply-To: <YWiS2J8qdrAitOUZ@robh.at.kernel.org>

On Thu, 14 Oct 2021 15:28:08 -0500
Rob Herring <robh@kernel.org> wrote:

> On Wed, 06 Oct 2021 21:30:55 +0500, Nikita Travkin wrote:
> > Add vendor prefix for LITE-ON Technology Corp.
> > 
> > Signed-off-by: Nikita Travkin <nikita@trvn.ru>
> > ---
> >  Documentation/devicetree/bindings/vendor-prefixes.yaml | 2 ++
> >  1 file changed, 2 insertions(+)
> >   
> 
> Acked-by: Rob Herring <robh@kernel.org>

Series applied to the togreg branch of iio.git which is initially pushed
out as testing for 0-day to see if it can find anything we missed.

Thanks,

Jonathan

      reply	other threads:[~2021-10-16 15:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-06 16:30 [PATCH 1/4] dt-bindings: vendor-prefixes: Document liteon vendor prefix Nikita Travkin
2021-10-06 16:30 ` [PATCH 2/4] dt-bindings: iio: light: Document ltr501 light sensor bindings Nikita Travkin
2021-10-14 20:28   ` Rob Herring
2021-10-06 16:30 ` [PATCH 3/4] iio: light: ltr501: Add rudimentary regulator support Nikita Travkin
2021-10-06 16:30 ` [PATCH 4/4] iio: light: ltr501: Add of_device_id table Nikita Travkin
2021-10-07 15:41 ` [PATCH 1/4] dt-bindings: vendor-prefixes: Document liteon vendor prefix Jonathan Cameron
2021-10-14 20:28 ` Rob Herring
2021-10-16 15:55   ` Jonathan Cameron [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=20211016165552.680b2438@jic23-huawei \
    --to=jic23@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nikita@trvn.ru \
    --cc=robh+dt@kernel.org \
    --cc=robh@kernel.org \
    --cc=stephan@gerhold.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.