From: Patrice Chotard <patrice.chotard@st.com>
To: Linus Torvalds <torvalds@linux-foundation.org>,
Linus Walleij <linus.walleij@linaro.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Laxman Dewangan <ldewangan@nvidia.com>
Subject: Re: [GIT PULL] pin control bulk changes for the v4.7 cycle
Date: Fri, 20 May 2016 09:13:20 +0200 [thread overview]
Message-ID: <573EB910.6040904@st.com> (raw)
In-Reply-To: <CA+55aFyaN=B34CEAdSPX7AnGPTc15K-+ogqjAS_2SA8qbkYmfQ@mail.gmail.com>
Hi Linus
Sorry for that. I have submitted the fix last week but Linus W. was busy
and didn't get time to merged it.
Patrice
On 05/19/2016 09:52 PM, Linus Torvalds wrote:
> On Thu, May 19, 2016 at 4:20 AM, Linus Walleij <linus.walleij@linaro.org> wrote:
>> This kernel cycle was quite calm when it comes to pin
>> control and there is really just one major change, and that
>> is the introduction of devm_pinctrl_register() managed
>> resources.
> WTF happened here?
>
> drivers/pinctrl/stm32/pinctrl-stm32.c: In function ‘stm32_pconf_dbg_show’:
> drivers/pinctrl/stm32/pinctrl-stm32.c:797:17: warning: too many
> arguments for format [-Wformat-extra-args]
> seq_printf(s, "%d - %s -%s", alt,
> ^
>
> Hmm?
>
> That's not a merge error, that comes from your tree, commit
> 3beed93c1617 ("pinctrl: stm32: Implement .pin_config_dbg_show()").
>
> I fixed it up in the merge, but I shouldn't have needed to.
>
> Linus
next prev parent reply other threads:[~2016-05-20 7:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-19 11:20 [GIT PULL] pin control bulk changes for the v4.7 cycle Linus Walleij
2016-05-19 19:52 ` Linus Torvalds
2016-05-20 7:13 ` Patrice Chotard [this message]
2016-05-23 13:29 ` 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=573EB910.6040904@st.com \
--to=patrice.chotard@st.com \
--cc=ldewangan@nvidia.com \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).