From: "J. Neuschäfer" <j.neuschaefer@gmx.net>
To: Tomer Maimon <tmaimon77@gmail.com>
Cc: "J. Neuschäfer" <j.neuschaefer@gmx.net>,
linus.walleij@linaro.org, avifishman70@gmail.com,
tali.perry1@gmail.com, joel@jms.id.au, venture@google.com,
yuenn@google.com, benjaminfair@google.com,
linux-gpio@vger.kernel.org, openbmc@lists.ozlabs.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 4/7] pinctrl: nuvoton: npcm8xx: remove unused smb4den pin, group, function
Date: Thu, 18 Jul 2024 22:58:13 +0200 [thread overview]
Message-ID: <ZpmB5XHvEsiER6Ee@probook> (raw)
In-Reply-To: <CAP6Zq1gYSiXFhtA0HAaoSLD7Lz-9nuoy-cUn+qvh0BLev_ifVg@mail.gmail.com>
On Tue, Jul 16, 2024 at 05:24:11PM +0300, Tomer Maimon wrote:
> Hi,
>
> It does not exist, do you suggest modifying the "unused" to "not exist"?
Yes, that would be clearer in my opinion.
Best regards,
Jonathan
next prev parent reply other threads:[~2024-07-18 20:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-11 19:37 [PATCH v1 0/7] pinctrl: npcm8xx: pin configuration changes Tomer Maimon
2024-07-11 19:37 ` [PATCH v1 1/7] pinctrl: nuvoton: npcm8xx: clear polarity before set both edge Tomer Maimon
2024-07-11 19:37 ` [PATCH v1 2/7] pinctrl: nuvoton: npcm8xx: add gpi35 and gpi36 Tomer Maimon
2024-07-11 19:37 ` [PATCH v1 3/7] pinctrl: nuvoton: npcm8xx: add pin 250 to DDR pins group Tomer Maimon
2024-07-11 19:37 ` [PATCH v1 4/7] pinctrl: nuvoton: npcm8xx: remove unused smb4den pin, group, function Tomer Maimon
2024-07-12 17:45 ` J. Neuschäfer
2024-07-16 14:24 ` Tomer Maimon
2024-07-18 20:58 ` J. Neuschäfer [this message]
2024-07-18 22:05 ` Tomer Maimon
2024-07-11 19:37 ` [PATCH v1 5/7] pinctrl: nuvoton: npcm8xx: remove unused lpcclk " Tomer Maimon
2024-07-11 19:37 ` [PATCH v1 6/7] pinctrl: nuvoton: npcm8xx: modify clkrun and serirq pin configuration Tomer Maimon
2024-07-11 19:37 ` [PATCH v1 7/7] pinctrl: nuvoton: npcm8xx: modify pins flags Tomer Maimon
2024-07-13 12:35 ` [PATCH v1 0/7] pinctrl: npcm8xx: pin configuration changes Jonas Gorski
2024-07-16 14:24 ` Tomer Maimon
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=ZpmB5XHvEsiER6Ee@probook \
--to=j.neuschaefer@gmx.net \
--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=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).