From: Conor Dooley <conor@kernel.org>
To: Andy Shevchenko <andriy.shevchenko@intel.com>
Cc: Linus Walleij <linusw@kernel.org>,
Conor Dooley <conor.dooley@microchip.com>,
Xianwei Zhao <xianwei.zhao@amlogic.com>,
Neil Armstrong <neil.armstrong@linaro.org>,
Kevin Hilman <khilman@baylibre.com>,
Jerome Brunet <jbrunet@baylibre.com>,
Martin Blumenstingl <martin.blumenstingl@googlemail.com>,
linux-amlogic@lists.infradead.org, linux-gpio@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [RFC] pinctrl: pinconf-generic: move ..dt_node_to_map_pinmux() to amlogic-am4 driver
Date: Wed, 4 Feb 2026 17:08:37 +0000 [thread overview]
Message-ID: <20260204-claim-chemist-5dbaeabf8b8e@spud> (raw)
In-Reply-To: <aYNw-k1q_vuP-4DZ@smile.fi.intel.com>
[-- Attachment #1: Type: text/plain, Size: 409 bytes --]
On Wed, Feb 04, 2026 at 06:16:58PM +0200, Andy Shevchenko wrote:
>
> TL;DR: My point that double dots is confusing and non-standard way to refer to
> something which is cut. If not full, ideally it can use triple dots followed by
> underscore
>
> pinconf-generic: move ..._dt_node_to_map_pinmux() to amlogic-am4 driver
This looks good to me. Linus, want a resend or will you adapt it
yourself?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2026-02-04 17:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-03 16:17 [RFC] pinctrl: pinconf-generic: move ..dt_node_to_map_pinmux() to amlogic-am4 driver Conor Dooley
2026-02-03 23:34 ` Linus Walleij
2026-02-04 8:05 ` Andy Shevchenko
2026-02-04 14:15 ` Conor Dooley
2026-02-04 14:22 ` Andy Shevchenko
2026-02-04 14:26 ` Andy Shevchenko
2026-02-04 15:50 ` Conor Dooley
2026-02-04 16:16 ` Andy Shevchenko
2026-02-04 17:08 ` Conor Dooley [this message]
2026-02-06 11:08 ` 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=20260204-claim-chemist-5dbaeabf8b8e@spud \
--to=conor@kernel.org \
--cc=andriy.shevchenko@intel.com \
--cc=conor.dooley@microchip.com \
--cc=jbrunet@baylibre.com \
--cc=khilman@baylibre.com \
--cc=linusw@kernel.org \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.blumenstingl@googlemail.com \
--cc=neil.armstrong@linaro.org \
--cc=xianwei.zhao@amlogic.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