Linux-Amlogic Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: Neil Armstrong <narmstrong@baylibre.com>
Cc: linux-amlogic@lists.infradead.org,
	U-Boot Mailing List <u-boot@lists.denx.de>
Subject: Re: [PULL u-boot] Please pull u-boot-amlogic-20190129
Date: Tue, 29 Jan 2019 21:19:13 -0500	[thread overview]
Message-ID: <20190130021913.GS30838@bill-the-cat> (raw)
In-Reply-To: <65195f2f-1a96-babe-a08d-aa9f2899de33@baylibre.com>


[-- Attachment #1.1: Type: text/plain, Size: 775 bytes --]

On Tue, Jan 29, 2019 at 11:22:15AM +0100, Neil Armstrong wrote:

> Hi Tom,
> 
> Here is single patch adding support for pinconf on the amlogic pinctrl driver,
> fixed after a build failure report from Anatolij.
> This PR replaces u-boot-amlogic-20190128.
> 
> Thanks,
> Neil
> 
> The following changes since commit 0da90255083681a02b24528f80da9d4062ff634a:
> 
>   Merge branch '2019-01-25-master-imports' (2019-01-26 22:47:55 -0500)
> 
> are available in the Git repository at:
> 
>   git://git.denx.de/u-boot-amlogic.git tags/u-boot-amlogic-20190129
> 
> for you to fetch changes up to c4c726c26bdc09a2c907e230fdf6c75adcc2b674:
> 
>   pinctrl: meson: add pinconf support (2019-01-29 11:19:15 +0100)
> 

Applied to u-boot/master, thanks!

-- 
Tom

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

[-- Attachment #2: Type: text/plain, Size: 167 bytes --]

_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic

      reply	other threads:[~2019-01-30  2:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-29 10:22 [PULL u-boot] Please pull u-boot-amlogic-20190129 Neil Armstrong
2019-01-30  2:19 ` Tom Rini [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=20190130021913.GS30838@bill-the-cat \
    --to=trini@konsulko.com \
    --cc=linux-amlogic@lists.infradead.org \
    --cc=narmstrong@baylibre.com \
    --cc=u-boot@lists.denx.de \
    /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