From: "Jonathan Neuschäfer" <j.neuschaefer@gmx.net>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: "Jonathan Neuschäfer" <j.neuschaefer@gmx.net>,
"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Joel Stanley" <joel@jms.id.au>
Subject: Re: [PATCH 0/2] Fixing the compile-test warnings in pinctrl-npcm7xx
Date: Thu, 3 Feb 2022 14:25:05 +0100 [thread overview]
Message-ID: <YfvXsZYYA7+0U9P0@latitude> (raw)
In-Reply-To: <CAHp75VdtTzkXVY21WZje1EkqixOOxxA3M09NfqQanV0XSRiNjQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 478 bytes --]
On Wed, Feb 02, 2022 at 04:20:11PM +0200, Andy Shevchenko wrote:
> On Wed, Feb 2, 2022 at 2:54 PM Jonathan Neuschäfer
> <j.neuschaefer@gmx.net> wrote:
> >
> > My "Nuvoton WPCM450 pinctrl and GPIO driver" patchset brought two
> > warnings[1] in the pinctrl-npcm7xx to light. Here's an attempt at fixing
> > them.
>
> With added the respective Fixes tag to each of them
Good idea.
> Reviewed-by: Andy Shevchenko <andy.shevchenko@gmail.com>
Thanks!
Jonathan
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2022-02-03 13:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-02 12:54 [PATCH 0/2] Fixing the compile-test warnings in pinctrl-npcm7xx Jonathan Neuschäfer
2022-02-02 12:54 ` [PATCH 1/2] pinctrl: nuvoton: npcm7xx: Use %zd printk format for ARRAY_SIZE() Jonathan Neuschäfer
2022-02-11 1:00 ` Linus Walleij
2022-02-02 12:54 ` [PATCH 2/2] pinctrl: nuvoton: npcm7xx: Rename DS() macro to DSTR() Jonathan Neuschäfer
2022-02-02 14:20 ` [PATCH 0/2] Fixing the compile-test warnings in pinctrl-npcm7xx Andy Shevchenko
2022-02-03 13:25 ` Jonathan Neuschäfer [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=YfvXsZYYA7+0U9P0@latitude \
--to=j.neuschaefer@gmx.net \
--cc=andy.shevchenko@gmail.com \
--cc=joel@jms.id.au \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@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 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).