From: John Crispin <blogic@openwrt.org>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: "linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>
Subject: Re: [PATCH 1/3] pinctrl: lantiq: 2 pins have the wrong mux list
Date: Tue, 5 Jan 2016 11:10:32 +0100 [thread overview]
Message-ID: <568B9698.6060101@openwrt.org> (raw)
In-Reply-To: <CACRpkdZbJBTW2WbzR0K+afTvvP_y2scjtnnJv3frLfU5ki_b2w@mail.gmail.com>
On 05/01/2016 11:03, Linus Walleij wrote:
> On Mon, Jan 4, 2016 at 10:27 PM, John Crispin <blogic@openwrt.org> wrote:
>
>> The latest vendor SDK contained this patch.
>>
>> Signed-off-by: John Crispin <blogic@openwrt.org>
>
> Patch applied. Had to rebase it manually for some reason.
>
> Yours,
> Linus Walleij
>
weird, it was generated using git on top of v4.4-rc7
thanks and sorry for the extra hassle.
John
next prev parent reply other threads:[~2016-01-05 10:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-04 21:27 [PATCH 1/3] pinctrl: lantiq: 2 pins have the wrong mux list John Crispin
2016-01-04 21:27 ` [PATCH 2/3] pinctrl: lantiq: set the OD bit when the pin it an output John Crispin
2016-01-05 10:05 ` Linus Walleij
2016-01-05 10:11 ` John Crispin
2016-01-05 10:18 ` Linus Walleij
2016-01-04 21:27 ` [PATCH 3/3] pinctrl: lantiq: add a to_irq callback John Crispin
2016-01-05 10:10 ` Linus Walleij
2016-01-05 12:59 ` Martin Schiller
2016-01-05 14:19 ` Linus Walleij
2016-03-31 4:44 ` Martin Schiller
2016-04-01 13:22 ` Linus Walleij
2016-01-05 10:03 ` [PATCH 1/3] pinctrl: lantiq: 2 pins have the wrong mux list Linus Walleij
2016-01-05 10:10 ` John Crispin [this message]
2016-01-05 12:59 ` Martin Schiller
2016-01-05 13:19 ` Linus Walleij
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=568B9698.6060101@openwrt.org \
--to=blogic@openwrt.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.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 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.