linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chris Ruehl <chris.ruehl@gtsys.com.hk>
To: "Linus Walleij" <linus.walleij@linaro.org>,
	"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: Shawn Guo <shawn.guo@linaro.org>,
	Sascha Hauer <kernel@pengutronix.de>,
	Markus Pargmann <mpa@pengutronix.de>,
	"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>
Subject: Re: [Resend][PATCH] Pinctrl: imx1: fix wrong pin-name resolving
Date: Fri, 17 Jul 2015 09:33:13 +0800	[thread overview]
Message-ID: <55A85B59.5060906@gtsys.com.hk> (raw)
In-Reply-To: <CACRpkdawo3048Kt-_Jio0kgSkUU5mkKkZ4gAJRZom3uKisEF0A@mail.gmail.com>

>>>
>>> Patch applied. Can't seem so see anyone who's safeguarding this
>>> driver recently, putting some people on To:
>>
>> I commented in that thread and the outcome from my POV was that the fix
>> needs a better changelog and it could be optimised to not lookup the pin
>> if debug is off. (I don't know the patch content, as it was stripped in
>> the reply.)
>
> OK Chris will you send a new version of this patch?
>
> Yours,
> Linus Walleij
>

Hi Uwe

If you don't mind take over the ownership of patching this issue?

I'm very busy at the moment and afraid it takes too long to bring the right
comments etc..

Thanks
Chris


-- 
GTSYS Limited RFID Technology
9/F, Unit E, R07, Kwai Shing Industrial Building Phase 2,
42-46 Tai Lin Pai Road, Kwai Chung, N.T., Hong Kong
Tel (852) 9079 9521

Disclaimer: http://www.gtsys.com.hk/email/classified.html

  reply	other threads:[~2015-07-17  1:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-26  0:26 [Resend][PATCH] Pinctrl: imx1: fix wrong pin-name resolving Chris Ruehl
2015-07-16  8:52 ` Linus Walleij
2015-07-16 11:34   ` Uwe Kleine-König
2015-07-16 14:00     ` Linus Walleij
2015-07-17  1:33       ` Chris Ruehl [this message]
2015-07-17  7:38         ` [PATCH] Subject: pinctrl: imx1-core: Fix debug output in .pin_config_set callback Uwe Kleine-König
2015-07-17  7:56           ` Markus Pargmann
2015-07-17  7:58           ` 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=55A85B59.5060906@gtsys.com.hk \
    --to=chris.ruehl@gtsys.com.hk \
    --cc=kernel@pengutronix.de \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=mpa@pengutronix.de \
    --cc=shawn.guo@linaro.org \
    --cc=u.kleine-koenig@pengutronix.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;
as well as URLs for NNTP newsgroup(s).