From: Stephen Warren <swarren@nvidia.com>
To: Stephen Warren <swarren@nvidia.com>,
Linus Walleij <linus.walleij@stericsson.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Cc: Grant Likely <grant.likely@secretlab.ca>,
Barry Song <21cnbao@gmail.com>,
Shawn Guo <shawn.guo@freescale.com>,
Thomas Abraham <thomas.abraham@linaro.org>,
Dong Aisheng <dong.aisheng@linaro.org>,
Rajendra Nayak <rajendra.nayak@linaro.org>,
Haojian Zhuang <haojian.zhuang@marvell.com>,
Linus Walleij <linus.walleij@linaro.org>
Subject: RE: [PATCH] pinctrl: resurrect verbose pinmux-pins
Date: Fri, 2 Mar 2012 09:41:04 -0800 [thread overview]
Message-ID: <74CDBE0F657A3D45AFBB94109FB122FF17BE861991@HQMAIL01.nvidia.com> (raw)
In-Reply-To: <74CDBE0F657A3D45AFBB94109FB122FF17BE861978@HQMAIL01.nvidia.com>
Stephen Warren wrote at Friday, March 02, 2012 10:22 AM:
> Linus Walleij wrote at riday, March 02, 2012 9:31 AM:
> > From: Linus Walleij <linus.walleij@linaro.org>
> >
> > This reintroduces the verbosity in the pinmux-pins file, now this
> > file will list all pins, their names, owning device (and if it's
> > a hog) and also in applicable cases the function and group making
> > use of that pin right now.
> >
> > Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
>
> It'd be nice if we could defer this fix until after all the API rework,
> because it'll cause all kinds of conflicts otherwise.
Oh, I see this patch is in your for-next branch already before I had a chance
to comment on it. I guess I'll have write a patch to convert the removed struct
type to char*s and rebase on top of it:-(
--
nvpublic
next prev parent reply other threads:[~2012-03-02 17:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-02 16:31 Linus Walleij
2012-03-02 17:22 ` Stephen Warren
2012-03-02 17:41 ` Stephen Warren [this message]
2012-03-02 18:24 ` Stephen Warren
2012-03-05 10:15 ` 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=74CDBE0F657A3D45AFBB94109FB122FF17BE861991@HQMAIL01.nvidia.com \
--to=swarren@nvidia.com \
--cc=21cnbao@gmail.com \
--cc=dong.aisheng@linaro.org \
--cc=grant.likely@secretlab.ca \
--cc=haojian.zhuang@marvell.com \
--cc=linus.walleij@linaro.org \
--cc=linus.walleij@stericsson.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rajendra.nayak@linaro.org \
--cc=shawn.guo@freescale.com \
--cc=thomas.abraham@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
all inboxes | Powered by JetHome®