From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH v4 00/88] PFC pinctrl functions for sh7372, sh73a0, r8a7740 and r8a7779
Date: Thu, 14 Mar 2013 13:39:35 +0000 [thread overview]
Message-ID: <3618543.7NdQnm2iZo@avalon> (raw)
In-Reply-To: <1363215633-4264-1-git-send-email-laurent.pinchart+renesas@ideasonboard.com>
Hi Linus,
On Thursday 14 March 2013 14:31:09 Linus Walleij wrote:
> On Thu, Mar 14, 2013 at 1:54 PM, Laurent Pinchart wrote:
> >> It seems like some Kconfig updates might be in order.
> >
> > I see two ways to fix this but I'm not sure which one is best. The first
> > one handles the issue in the pinctrl core:
>
> And that is what we want to do.
>
> > -#ifdef CONFIG_GENERIC_PINCONF
> > +#if defined(CONFIG_GENERIC_PINCONF) && defined (CONFIG_DEBUG_FS)
>
> I merged a patch like this only yesterday to my fixes branch.
>
> commit bf4d7be57ba9040347065f48a60f895a254f6e28
> Author: Sachin Kamat <sachin.kamat@linaro.org>
> Date: Wed Mar 13 17:13:46 2013 +0530
> pinctrl: generic: Fix compilation error
Great, thank you. Is that patch present in a stable branch that Simon could
merge ?
> > @@ -365,7 +365,9 @@ static const struct pinconf_ops sh_pfc_pinconf_ops = {
> > .pin_config_get = sh_pfc_pinconf_get,
> > .pin_config_set = sh_pfc_pinconf_set,
> > .pin_config_group_set = sh_pfc_pinconf_group_set,
> > +#ifdef CONFIG_DEBUG_FS
> > .pin_config_config_dbg_show = pinconf_generic_dump_config,
> > +#endif
> >
> > };
>
> Is that necessary? Well it makes it harder to do the wrong thing...
>
> Can you send a separate patch like this?
With the above patch merged in your tree no modification to sh-pfc is needed
anymore.
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2013-03-14 13:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-13 22:59 [PATCH v4 00/88] PFC pinctrl functions for sh7372, sh73a0, r8a7740 and r8a7779 Laurent Pinchart
2013-03-14 9:20 ` Simon Horman
2013-03-14 9:46 ` Simon Horman
2013-03-14 12:54 ` Laurent Pinchart
2013-03-14 13:31 ` Linus Walleij
2013-03-14 13:39 ` Laurent Pinchart [this message]
2013-03-14 13:55 ` Linus Walleij
2013-03-14 14:01 ` Laurent Pinchart
2013-03-14 15:09 ` Linus Walleij
2013-03-14 15:13 ` Laurent Pinchart
2013-03-15 6:25 ` Simon Horman
2013-03-15 12:35 ` Laurent Pinchart
2013-03-15 15:37 ` Simon Horman
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=3618543.7NdQnm2iZo@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=linux-sh@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.