Linux-MIPS Archive mirror
 help / color / mirror / Atom feed
From: Bartosz Golaszewski <brgl@kernel.org>
To: Manuel Lauss <manuel.lauss@gmail.com>
Cc: Bartosz Golaszewski <bartosz.golaszewski@oss.qualcomm.com>,
	 Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
	Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	 linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/6] MIPS: alchemy: attach software nodes to GPIO controllers and use properties
Date: Tue, 19 May 2026 13:52:16 +0200	[thread overview]
Message-ID: <CAMRc=Md6=Zn0CDt9=UsFWtT7FesefKEKk3jrvhhKTL9zPFPL1Q@mail.gmail.com> (raw)
In-Reply-To: <CAOLZvyENGzU7NqedQCfT3dcchUJjxRr-WJWC4ubqViLD6yzTUg@mail.gmail.com>

On Tue, May 5, 2026 at 3:31 PM Manuel Lauss <manuel.lauss@gmail.com> wrote:
>
> Hello Bartosz,
>
> On Tue, May 5, 2026 at 11:09 AM Bartosz Golaszewski
> <bartosz.golaszewski@oss.qualcomm.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 4 patches convert the remaining 2 boards to use software
> > nodes as well and fix some build warnings.
>
> I have run-tested this on the DB1300, without any issues.
> Tested-by: Manuel Lauss <manuel.lauss@gmail.com>
>
> Thanks a lot!
>       Manuel

Hi Thomas!

Can you please queue these for v7.2?

Thanks,
Bartosz

  reply	other threads:[~2026-05-19 11:52 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-05  9:04 [PATCH v2 0/6] MIPS: alchemy: attach software nodes to GPIO controllers and use properties Bartosz Golaszewski
2026-05-05  9:04 ` [PATCH v2 1/6] MIPS: alchemy: platform: add missing include Bartosz Golaszewski
2026-05-05  9:04 ` [PATCH v2 2/6] MIPS: alchemy: provide visible function prototypes to board files Bartosz Golaszewski
2026-05-05  9:04 ` [PATCH v2 3/6] MIPS: alchemy: mtx1: attach software nodes to GPIO chips Bartosz Golaszewski
2026-05-05  9:04 ` [PATCH v2 4/6] MIPS: alchemy: db1000: use nodes attached to GPIO chips in properties Bartosz Golaszewski
2026-05-05  9:04 ` [PATCH v2 5/6] MIPS: alchemy: gpr: switch to static device properties Bartosz Golaszewski
2026-05-05  9:04 ` [PATCH v2 6/6] MIPS: alchemy: db1300: " Bartosz Golaszewski
2026-05-05 13:31 ` [PATCH v2 0/6] MIPS: alchemy: attach software nodes to GPIO controllers and use properties Manuel Lauss
2026-05-19 11:52   ` Bartosz Golaszewski [this message]
2026-05-19 20:56     ` Thomas Bogendoerfer
2026-05-20  7:07       ` Bartosz Golaszewski
2026-05-26 14:35         ` Thomas Bogendoerfer

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=Md6=Zn0CDt9=UsFWtT7FesefKEKk3jrvhhKTL9zPFPL1Q@mail.gmail.com' \
    --to=brgl@kernel.org \
    --cc=bartosz.golaszewski@oss.qualcomm.com \
    --cc=dmitry.torokhov@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=manuel.lauss@gmail.com \
    --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).