linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Walleij <linus.walleij@linaro.org>
To: Stephen Warren <swarren@nvidia.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Chanho Park <chanho61.park@samsung.com>
Subject: Re: [PATCH] pinctrl: Fix pinconf_pins_show iteration
Date: Thu, 19 Jan 2012 19:32:49 +0100	[thread overview]
Message-ID: <CACRpkdYen==qdQMidskw5V6Q1=r-4hOv0K4OW4qkxwnBv+L-QA@mail.gmail.com> (raw)
In-Reply-To: <74CDBE0F657A3D45AFBB94109FB122FF1780DAB0F3@HQMAIL01.nvidia.com>

On Thu, Jan 19, 2012 at 6:52 PM, Stephen Warren <swarren@nvidia.com> wrote:
> Linus Walleij wrote at Tuesday, January 10, 2012 2:17 AM:
>> On Fri, Jan 6, 2012 at 9:38 PM, Stephen Warren <swarren@nvidia.com> wrote:
>>
>> > Commit 706e852 "pinctrl: correct a offset while enumerating pins"
>> > modified the variable used by pinconf_pin_show()'s for loop, but didn't
>> > update the for loop test expression.
>> >
>> > Signed-off-by: Stephen Warren <swarren@nvidia.com>
>>
>> OK applied to my fixes branch, will send this along with any other
>> fixes once Torvalds has pulled the pinctrl tree for this merge window.
>
> Linus,
>
> This still hasn't shown up in next-20120119. Is that expected?

Yes I was waiting for the merge window to close, but I guess that's
a bit over-cautios. I'll push it out tomorrow...

Thanks,
Linus Walleij

      reply	other threads:[~2012-01-19 18:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-06 20:38 [PATCH] pinctrl: Fix pinconf_pins_show iteration Stephen Warren
2012-01-07  3:51 ` Chanho Park
2012-01-10  9:16 ` Linus Walleij
2012-01-19 17:52   ` Stephen Warren
2012-01-19 18:32     ` Linus Walleij [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='CACRpkdYen==qdQMidskw5V6Q1=r-4hOv0K4OW4qkxwnBv+L-QA@mail.gmail.com' \
    --to=linus.walleij@linaro.org \
    --cc=chanho61.park@samsung.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=swarren@nvidia.com \
    /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).