From: "Jonathan Neuschäfer" <j.neuschaefer@gmx.net>
To: linux-gpio@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, "Joel Stanley" <joel@jms.id.au>,
"Andy Shevchenko" <andy.shevchenko@gmail.com>,
"Jonathan Neuschäfer" <j.neuschaefer@gmx.net>,
"kernel test robot" <lkp@intel.com>,
"Avi Fishman" <avifishman70@gmail.com>,
"Tomer Maimon" <tmaimon77@gmail.com>,
"Tali Perry" <tali.perry1@gmail.com>,
"Patrick Venture" <venture@google.com>,
"Nancy Yuen" <yuenn@google.com>,
"Benjamin Fair" <benjaminfair@google.com>,
"Linus Walleij" <linus.walleij@linaro.org>,
openbmc@lists.ozlabs.org
Subject: [PATCH v2 0/2] Fixing the compile-test warnings in pinctrl-npcm7xx
Date: Thu, 3 Feb 2022 14:37:34 +0100 [thread overview]
Message-ID: <20220203133736.246397-1-j.neuschaefer@gmx.net> (raw)
My "Nuvoton WPCM450 pinctrl and GPIO driver" patchset brought two
warnings[1] in the pinctrl-npcm7xx to light. This patchset fixes them,
and now also includes the appropriate "Fixes:" tags.
[1]: https://lore.kernel.org/lkml/202201292234.NpSNe4TD-lkp@intel.com/
Jonathan Neuschäfer (2):
pinctrl: nuvoton: npcm7xx: Use %zd printk format for ARRAY_SIZE()
pinctrl: nuvoton: npcm7xx: Rename DS() macro to DSTR()
drivers/pinctrl/nuvoton/pinctrl-npcm7xx.c | 160 +++++++++++-----------
1 file changed, 80 insertions(+), 80 deletions(-)
--
2.34.1
next reply other threads:[~2022-02-03 13:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-03 13:37 Jonathan Neuschäfer [this message]
2022-02-03 13:37 ` [PATCH v2 1/2] pinctrl: nuvoton: npcm7xx: Use %zd printk format for ARRAY_SIZE() Jonathan Neuschäfer
2022-02-03 14:16 ` Andy Shevchenko
2022-02-03 14:40 ` Jonathan Neuschäfer
2022-02-03 13:37 ` [PATCH v2 2/2] pinctrl: nuvoton: npcm7xx: Rename DS() macro to DSTR() Jonathan Neuschäfer
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=20220203133736.246397-1-j.neuschaefer@gmx.net \
--to=j.neuschaefer@gmx.net \
--cc=andy.shevchenko@gmail.com \
--cc=avifishman70@gmail.com \
--cc=benjaminfair@google.com \
--cc=joel@jms.id.au \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=openbmc@lists.ozlabs.org \
--cc=tali.perry1@gmail.com \
--cc=tmaimon77@gmail.com \
--cc=venture@google.com \
--cc=yuenn@google.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 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).