devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Walleij <linus.walleij@linaro.org>
To: Charles Keepax <ckeepax@opensource.cirrus.com>
Cc: Rob Herring <robh+dt@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	patches@opensource.cirrus.com,
	"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
	"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
	<devicetree@vger.kernel.org>
Subject: Re: [PATCH v8 RESEND 1/2] pinctrl: lochnagar: Add initial binding documentation
Date: Thu, 4 Apr 2019 12:08:58 +0700	[thread overview]
Message-ID: <CACRpkdb4ETLC69eX_omTdGfZvtBAspcpsOejXg3+q4QGCri89A@mail.gmail.com> (raw)
In-Reply-To: <20190319134851.10420-1-ckeepax@opensource.cirrus.com>

On Tue, Mar 19, 2019 at 8:48 PM Charles Keepax
<ckeepax@opensource.cirrus.com> wrote:

> Lochnagar is an evaluation and development board for Cirrus
> Logic Smart CODEC and Amp devices. It allows the connection of
> most Cirrus Logic devices on mini-cards, as well as allowing
> connection of various application processor systems to provide a
> full evaluation platform. This driver supports the board
> controller chip on the Lochnagar board.
>
> Signed-off-by: Charles Keepax <ckeepax@opensource.cirrus.com>
> Reviewed-by: Rob Herring <robh@kernel.org>
> Acked-by: Linus Walleij <linus.walleij@linaro.org>

Patch applied to the pinctrl tree.

Yours,
Linus Walleij

      parent reply	other threads:[~2019-04-04  5:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-19 13:48 [PATCH v8 RESEND 1/2] pinctrl: lochnagar: Add initial binding documentation Charles Keepax
2019-03-19 13:48 ` [PATCH v8 RESEND 2/2] pinctrl: lochnagar: Add support for the Cirrus Logic Lochnagar Charles Keepax
2019-04-01  8:35   ` Charles Keepax
2019-04-04  5:10   ` Linus Walleij
2019-04-04  5:08 ` Linus Walleij [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=CACRpkdb4ETLC69eX_omTdGfZvtBAspcpsOejXg3+q4QGCri89A@mail.gmail.com \
    --to=linus.walleij@linaro.org \
    --cc=ckeepax@opensource.cirrus.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=patches@opensource.cirrus.com \
    --cc=robh+dt@kernel.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).