From: Chanho Park <chanho61.park@samsung.com>
To: "'Linus Walleij'" <linus.walleij@linaro.org>
Cc: "'Stephen Warren'" <swarren@nvidia.com>,
Barry.Song@csr.com, Rongjun.Ying@csr.com,
linux-kernel@vger.kernel.org,
"'Kyungmin Park'" <kyungmin.park@samsung.com>
Subject: RE: [PATCHv2] drivers: pinctrl: add a pin_base for sparse gpio-ranges
Date: Thu, 10 Nov 2011 17:22:03 +0900 [thread overview]
Message-ID: <00e701cc9f81$d3a6bfe0$7af43fa0$%park@samsung.com> (raw)
In-Reply-To: <CACRpkdZ80Tj_ttsQTAZAUT4X_UfQi9PDn2Tjc35jT62nBd496A@mail.gmail.com>
Hi, Linus.
Our smtp server blocked my email. :)
I'll submit v3 patch soon. (Maybe tomorrow)
Thank you.
Best Regards,
Chanho Park
> -----Original Message-----
> From: linux-kernel-owner@vger.kernel.org [mailto:linux-kernel-
> owner@vger.kernel.org] On Behalf Of Linus Walleij
> Sent: Thursday, November 10, 2011 5:08 PM
> To: Chanho Park
> Cc: Stephen Warren; Barry.Song@csr.com; Rongjun.Ying@csr.com; linux-
> kernel@vger.kernel.org; Kyungmin Park
> Subject: Re: [PATCHv2] drivers: pinctrl: add a pin_base for sparse
> gpio-ranges
>
> On Wed, Nov 2, 2011 at 9:56 AM, Chanho Park <chanho61.park@samsung.com>
> wrote:
>
> >> You'll need to update that documentation now that the final
> parameter is
> >> a pin number, not an offset into the range.
> >
> > I'll update it. Thx.
>
> Chanho, do you have a v3 ready? I'd really like to apply this patch...
>
> Yours,
> Linus Walleij
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel"
> in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2011-11-10 8:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-28 5:41 Chanho Park
2011-10-28 16:13 ` Stephen Warren
2011-11-02 8:56 ` Chanho Park
2011-11-10 8:08 ` Linus Walleij
2011-11-10 8:22 ` Chanho Park [this message]
2011-11-04 16:13 ` Thomas Abraham
2011-11-07 4:04 ` Chanho Park
2011-11-07 4:12 ` Thomas Abraham
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='00e701cc9f81$d3a6bfe0$7af43fa0$%park@samsung.com' \
--to=chanho61.park@samsung.com \
--cc=Barry.Song@csr.com \
--cc=Rongjun.Ying@csr.com \
--cc=kyungmin.park@samsung.com \
--cc=linus.walleij@linaro.org \
--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
all inboxes | Powered by JetHome®