From: Martin Schiller <mschiller@tdt.de>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: John Crispin <blogic@openwrt.org>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>
Subject: RE: [PATCH 3/3] pinctrl: lantiq: add a to_irq callback
Date: Thu, 31 Mar 2016 04:44:51 +0000 [thread overview]
Message-ID: <165cccb7239e476e953c2e93d8aec9ce@TDT-MS.TDTNET.local> (raw)
In-Reply-To: <CACRpkdaqCdOC4w7n7oXTAoc6KgZjB1z+SNEEs4bEhObtPF+ntQ@mail.gmail.com>
Hi Linus,
On 01/05/2016 at 3:19 PM, Linus Walleij wrote:
> On Tue, Jan 5, 2016 at 1:59 PM, Martin Schiller <mschiller@tdt.de> wrote:
>
> > As I submitted this change a few weeks ago, you already applied this in the
> linux-gpio tree here:
> > https://git.kernel.org/cgit/linux/kernel/git/linusw/linux-
> gpio.git/commit/drivers/pinctrl/pinctrl-
> xway.c?h=devel&id=3e640743fee6e6a82ead1f163737755b2a965712
>
> Yeah I noticed.... hehe it blew up in my face when I tried to merge
> the pin control and GPIO trees to see what happens in Linux-next.
> I think I figured it out now...
I think there still went something wrong with this commit:
In the commit log you can see that this changes are added on 2015-12-10 and
then reverted on 2016-01-05.
- Martin
next prev parent reply other threads:[~2016-03-31 5:23 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 [this message]
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
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=165cccb7239e476e953c2e93d8aec9ce@TDT-MS.TDTNET.local \
--to=mschiller@tdt.de \
--cc=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.