From: Eugeniu Rosca <roscaeugeniu@gmail.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Eugeniu Rosca <roscaeugeniu@gmail.com>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
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 17:20:04 +0100 [thread overview]
Message-ID: <20170319162004.GB8580@x230> (raw)
In-Reply-To: <CAMuHMdWzHLDjXknbK+Vik-7Qyi_WgcZL4JB5U_srKMh1sZa7Vg@mail.gmail.com>
On Sun, Mar 19, 2017 at 03:02:48PM +0100, Geert Uytterhoeven wrote:
Hi Geert,
> Thanks for your patch!
> But next time, please send it inline, for easier commenting.
Thanks! Will do that next time.
> 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).
Agree! It's good that printing the correct PFC driver name is already
fixed on your side.
Best regards,
Eugeniu.
prev parent reply other threads:[~2017-03-19 16:20 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
2017-03-19 16:20 ` Eugeniu Rosca [this message]
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=20170319162004.GB8580@x230 \
--to=roscaeugeniu@gmail.com \
--cc=geert@linux-m68k.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linus.walleij@linaro.org \
--cc=linux-renesas-soc@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.