From: "Heiko Stübner" <heiko@sntech.de>
To: Bartosz Golaszewski <brgl@bgdev.pl>
Cc: kernel test robot <lkp@intel.com>,
Quentin Schulz <quentin.schulz@cherry.de>,
oe-kbuild-all@lists.linux.dev
Subject: Re: [linux-next:master 5345/5954] arch/arm64/boot/dts/rockchip/px30-ringneck-haikou-haikou-video-demo.dtb: gpio@27: 'reset-gpios' does not match any of the regexes: '^(.+-hog(-[0-9]+)?)$', 'pinctrl-[0-9]+'
Date: Tue, 25 Feb 2025 11:45:12 +0100 [thread overview]
Message-ID: <21492727.0c2gjJ1VT2@diego> (raw)
In-Reply-To: <CAMRc=Me11Sf-UKW3Fj-cwpKgbEvg--yF4fUZ8ioH+XLixt_APw@mail.gmail.com>
Am Dienstag, 25. Februar 2025, 11:32:00 MEZ schrieb Bartosz Golaszewski:
> On Tue, Feb 25, 2025 at 11:29 AM Heiko Stübner <heiko@sntech.de> wrote:
> > Am Dienstag, 25. Februar 2025, 11:08:23 MEZ schrieb Quentin Schulz:
> > > On 2/24/25 11:09 PM, kernel test robot wrote:
> > With the patch-series for the PCA967x in question [0] not getting any more
> > change requests, I suppose Linus or Bartosz might even apply it in the near
> > future, so I'll give it some days and if that doesn't come true, I'll drop
> > the board patches here.
> >
> > Heiko
> >
> >
> > [0] https://lore.kernel.org/linux-gpio/20250224-pca976x-reset-driver-v3-0-58370ef405be@cherry.de/T/#m34648451131d34ba85538e08da0cacfc366d91af
> >
> >
>
> v3 was submitted yesterday. I will certainly queue it for v6.15, don't worry.
that was my thinking too ... I should've spelled out the "v3 was submitted
only yesterday" in my reply though ;-)
Heiko
prev parent reply other threads:[~2025-02-25 10:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-24 22:09 [linux-next:master 5345/5954] arch/arm64/boot/dts/rockchip/px30-ringneck-haikou-haikou-video-demo.dtb: gpio@27: 'reset-gpios' does not match any of the regexes: '^(.+-hog(-[0-9]+)?)$', 'pinctrl-[0-9]+' kernel test robot
2025-02-25 10:08 ` Quentin Schulz
2025-02-25 10:29 ` Heiko Stübner
2025-02-25 10:32 ` Bartosz Golaszewski
2025-02-25 10:45 ` Heiko Stübner [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=21492727.0c2gjJ1VT2@diego \
--to=heiko@sntech.de \
--cc=brgl@bgdev.pl \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=quentin.schulz@cherry.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.