From: Bartosz Golaszewski <brgl@kernel.org>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/4] MIPS: alchemy: attach software nodes to GPIO controllers and use properties
Date: Thu, 30 Apr 2026 11:30:49 +0200 [thread overview]
Message-ID: <CAMRc=MdRFzSs9Z1BxJVN+zq8DbzRwWPa_E3M+c1LRYQNp=qKFA@mail.gmail.com> (raw)
In-Reply-To: <20260309-alchemy-v1-0-f55e9dc60ba1@gmail.com>
On Tue, Mar 10, 2026 at 7:12 AM Dmitry Torokhov
<dmitry.torokhov@gmail.com> wrote:
>
> This series of patches updates board previously converted to use static
> device properties/software nodes to attach and use nodes attached to the
> respective gpiochip devices rather than simply defining unattached
> software nodes with matching name. This is a requirement of newer
> gpiolib code. Note that there is currently a workaround preserving the
> lookup based on the software node name, but it will be removed soon.
>
> The additional 2 patches convert the remaining 2 boards to use software
> nodes as well.
>
> Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
> ---
Hi Dmitry!
This missed the last merge window. Do you indent to resend it using
the new swnode field in struct platform_device_info?
Bart
prev parent reply other threads:[~2026-04-30 9:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-10 6:11 [PATCH 0/4] MIPS: alchemy: attach software nodes to GPIO controllers and use properties Dmitry Torokhov
2026-03-10 6:11 ` [PATCH 1/4] MIPS: alchemy: mtx1: attach software nodes to GPIO chips Dmitry Torokhov
2026-03-10 6:11 ` [PATCH 2/4] MIPS: alchemy: db1000: use nodes attached to GPIO chips in properties Dmitry Torokhov
2026-03-10 6:12 ` [PATCH 3/4] MIPS: alchemy: gpr: switch to static device properties Dmitry Torokhov
2026-03-10 6:12 ` [PATCH 4/4] MIPS: alchemy: db1300: " Dmitry Torokhov
2026-04-30 9:30 ` Bartosz Golaszewski [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='CAMRc=MdRFzSs9Z1BxJVN+zq8DbzRwWPa_E3M+c1LRYQNp=qKFA@mail.gmail.com' \
--to=brgl@kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=tsbogend@alpha.franken.de \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).