mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stephen Warren <swarren@nvidia.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH 2/2] pinctrl: Pass name instead of device to pin_config_*
Date: Mon, 19 Dec 2011 10:20:05 -0800	[thread overview]
Message-ID: <74CDBE0F657A3D45AFBB94109FB122FF176BE92A7E@HQMAIL01.nvidia.com> (raw)
In-Reply-To: <CACRpkdaKWcCReO27O6VjQNBCnSDu_tMLPLCkqR0aroUf7gLEVw@mail.gmail.com>

Linus Walleij wrote at Sunday, December 18, 2011 3:27 PM:
> On Fri, Dec 16, 2011 at 12:57 AM, Stephen Warren <swarren@nvidia.com> wrote:
> 
> > Obtaining a "struct pinctrl_dev *" is difficult for code not directly
> > related to the pinctrl subsystem. However, the device name of the pinctrl
> > device is fairly well known. So, modify pin_config_*() to take the device
> > name instead of the "struct pinctrl_dev *".
> >
> > Signed-off-by: Stephen Warren <swarren@nvidia.com>
> 
> Thanks Stephen, excellent, both applied.
> 
> I had to fix it up a bit to match the other
> refactoring patch I made so check the result in my tree or -next.

Yes, I think that looks fine, thanks.

Thanks for fixing up the documentation for me too.

BTW, do you know which commits you're planning on you're planning on
sending to mainline during the next merge window? If it includes these
two patches, I may be able to convert Tegra over to using the new pinctrl
driver in 3.3. And is your for-next branch stable (i.e. never rebased)
so that the arm-soc tree can use it as a dependency for my patches?

-- 
nvpublic


  reply	other threads:[~2011-12-19 18:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-15 23:57 [PATCH 1/2] pinctrl: Add "struct seq_file;" to pinconf.h Stephen Warren
2011-12-15 23:57 ` [PATCH 2/2] pinctrl: Pass name instead of device to pin_config_* Stephen Warren
2011-12-18 22:27   ` Linus Walleij
2011-12-19 18:20     ` Stephen Warren [this message]
2012-01-01 13:32       ` 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=74CDBE0F657A3D45AFBB94109FB122FF176BE92A7E@HQMAIL01.nvidia.com \
    --to=swarren@nvidia.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-kernel@vger.kernel.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®