From: Linus Walleij <linus.walleij@linaro.org>
To: Axel Lin <axel.lin@ingics.com>
Cc: Shawn Guo <shawn.guo@linaro.org>,
Dong Aisheng <dong.aisheng@linaro.org>,
Devendra Naga <devendra.aaru@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] pinctrl: imx: Fix the logic checking if not able to find pin reg map
Date: Thu, 15 Nov 2012 12:04:12 +0100 [thread overview]
Message-ID: <CACRpkdbXTa=b4Aja9FByzfu4c+bQcB0Ae0rKf033gi4WsEyS+A@mail.gmail.com> (raw)
In-Reply-To: <1352768407.19229.1.camel@phoenix>
On Tue, Nov 13, 2012 at 2:00 AM, Axel Lin <axel.lin@ingics.com> wrote:
> Current code sets "pin_reg = &info->pin_regs[i];" in each loop iteration,
> so in the case of no-match, pin_reg is not NULL.
>
> Signed-off-by: Axel Lin <axel.lin@ingics.com>
Thanks, applied with Dong's ACK.
Yours,
Linus Walleij
prev parent reply other threads:[~2012-11-15 11:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-13 1:00 [PATCH] pinctrl: imx: Fix the logic checking if not able to find pin reg map Axel Lin
2012-11-13 6:37 ` Dong Aisheng
2012-11-15 11:04 ` 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='CACRpkdbXTa=b4Aja9FByzfu4c+bQcB0Ae0rKf033gi4WsEyS+A@mail.gmail.com' \
--to=linus.walleij@linaro.org \
--cc=axel.lin@ingics.com \
--cc=devendra.aaru@gmail.com \
--cc=dong.aisheng@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shawn.guo@linaro.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).