All of lore.kernel.org
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Eugeniu Rosca <roscaeugeniu@gmail.com>
Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	Geert Uytterhoeven <geert+renesas@glider.be>,
	Linus Walleij <linus.walleij@linaro.org>,
	Linux-Renesas <linux-renesas-soc@vger.kernel.org>
Subject: Re: [PATCH] pinctrl: sh-pfc: Print correct pinmux info name
Date: Sun, 19 Mar 2017 15:02:48 +0100	[thread overview]
Message-ID: <CAMuHMdWzHLDjXknbK+Vik-7Qyi_WgcZL4JB5U_srKMh1sZa7Vg@mail.gmail.com> (raw)
In-Reply-To: <20170318205226.GA11403@x230>

Hi Eugeniu,

On Sat, Mar 18, 2017 at 9:52 PM, Eugeniu Rosca <roscaeugeniu@gmail.com> wrote:
> commit 0c151062f32c ("sh-pfc: Add support for SoC-specific
> initialization") allows defining SoC specific init functions.
> Such custom functions can register new pinmux info structures.
> Here is an example:
>
> static int my_pinmux_init(struct sh_pfc *pfc)
> {
>     if (my_criteria())
>         pfc->info = &new_pinmux_info;
> }
>
> A side effect of the pfc->info update in the above example is that
> the `const struct sh_pfc_soc_info *info` pointer used in the probe
> routine becomes outdated. One consequence of it is printing the wrong
> pinmux info structure name at the end of `sh_pfc_probe()`. Fix this.
>
> Signed-off-by: Eugeniu Rosca <erosca@de.adit-jv.com>

Thanks for your patch!
But next time, please send it inline, for easier commenting.

> ---
>  drivers/pinctrl/sh-pfc/core.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/pinctrl/sh-pfc/core.c b/drivers/pinctrl/sh-pfc/core.c
> index 6399eb1feb12..37fc70fb8e4d 100644
> --- a/drivers/pinctrl/sh-pfc/core.c
> +++ b/drivers/pinctrl/sh-pfc/core.c
> @@ -703,7 +703,7 @@ static int sh_pfc_probe(struct platform_device *pdev)
>
>       platform_set_drvdata(pdev, pfc);
>
> -     dev_info(pfc->dev, "%s support registered\n", info->name);
> +     dev_info(pfc->dev, "%s support registered\n", pfc->info->name);

>From a code maintenance point of view, I think it's safer to update the info
pointer itself, cfr. "[PATCH v2 1/4] pinctrl: sh-pfc: Update info pointer
after SoC-specific init"
(https://www.spinics.net/lists/linux-renesas-soc/msg12375.html).

Gr{oetje,eeting}s,

                        Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds

  reply	other threads:[~2017-03-19 14:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-18 20:52 [PATCH] pinctrl: sh-pfc: Print correct pinmux info name Eugeniu Rosca
2017-03-19 14:02 ` Geert Uytterhoeven [this message]
2017-03-19 16:20   ` Eugeniu Rosca

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=CAMuHMdWzHLDjXknbK+Vik-7Qyi_WgcZL4JB5U_srKMh1sZa7Vg@mail.gmail.com \
    --to=geert@linux-m68k.org \
    --cc=geert+renesas@glider.be \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=roscaeugeniu@gmail.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 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.