From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
Subject: Re: [GIT PULL] pin control fixes for the v4.2 series, take one
Date: Wed, 22 Jul 2015 09:08:44 +0200 [thread overview]
Message-ID: <20150722070844.GL9981@pengutronix.de> (raw)
In-Reply-To: <CACRpkdYz-a0A7i1sMj7=OZ1Vu8MnZEWtnD-ikQ1+HO5Cn_-DGw@mail.gmail.com>
Hello Linus,
On Tue, Jul 21, 2015 at 11:25:40PM +0200, Linus Walleij wrote:
> On Tue, Jul 21, 2015 at 8:47 PM, Uwe Kleine-König
> <u.kleine-koenig@pengutronix.de> wrote:
>
> > On Tue, Jul 21, 2015 at 08:36:04PM +0200, Linus Walleij wrote:
> >> Subject: pinctrl: imx1-core: Fix debug output in .pin_config_set callback
> > I remember seeing that "Subject: " in my patch stack, I thought I fixed
> > that and now it's to late for
>
> Ah, how could I miss that. Selective vision or something.
> Well let's see if Linus (the big penguin) want to fix it up, I
> can for one live with it.
if the other Linus fixes it, he probably need help from the NSA to not
break your signed tag. :-)
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | http://www.pengutronix.de/ |
--
To unsubscribe from this list: send the line "unsubscribe linux-gpio" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2015-07-22 7:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-21 18:36 [GIT PULL] pin control fixes for the v4.2 series, take one Linus Walleij
2015-07-21 18:47 ` Uwe Kleine-König
2015-07-21 21:25 ` Linus Walleij
2015-07-21 22:29 ` Linus Torvalds
2015-07-22 7:08 ` Uwe Kleine-König [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=20150722070844.GL9981@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sergei.shtylyov@cogentembedded.com \
--cc=torvalds@linux-foundation.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).