From: Lee Jones <lee@kernel.org>
To: Bartosz Golaszewski <brgl@kernel.org>
Cc: Linus Walleij <linusw@kernel.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Bartosz Golaszewski <bartosz.golaszewski@oss.qualcomm.com>,
linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org
Subject: Re: [PATCH v3 0/4] gpio: timberdale: remove platform data header
Date: Wed, 13 May 2026 14:39:50 +0100 [thread overview]
Message-ID: <20260513133950.GX305027@google.com> (raw)
In-Reply-To: <CAMRc=Md=eMGA4iSTJmd4_wBBDXEJRcbGyUQd5kjcFC6MGiy_fQ@mail.gmail.com>
On Mon, 11 May 2026, Bartosz Golaszewski wrote:
> On Thu, Apr 30, 2026 at 11:52 AM Lee Jones <lee@kernel.org> wrote:
> >
> > On Thu, 30 Apr 2026, Lee Jones wrote:
> >
> > > On Fri, 27 Mar 2026 11:49:06 +0100, Bartosz Golaszewski wrote:
> > > > There are several GPIO driver header scattered directly under
> > > > include/linux/. I'd like to either remove them or move then under
> > > > include/linux/gpio/. In case of gpio-timberdale, the platform data
> > > > struct can be replaced with generic device properties. This series does
> > > > that. It can go either though the MFD tree or GPIO with an Ack from Lee.
> > > >
> > > >
> > > > [...]
> > >
> > > Applied, thanks!
> > >
> > > [1/4] mfd: timberdale: move GPIO_NR_PINS into the driver
> > > commit: c44d171a52513bfd06b5d847b42b0c1013ddd46e
> > > [2/4] mfd: timberdale: set up a software node for the GPIO cell
> > > commit: 2012c0d1b91767b68dedac127c3575cf816313e1
> > > [3/4] gpio: timberdale: use device properties
> > > commit: 065d211f9ef7e60c510cbb3663ffdb7ca14efae2
> > > [4/4] gpio: timberdale: remove platform data header
> > > commit: 0cb4edca4ed1325ddeb368f80807403cc37edc00
> >
> > Note to self: ib-mfd-gpio-7.2
> >
> > --
> > Lee Jones
>
> Hi Lee!
>
> I received this notification from b4 but this series never made its
> way into linux-next. Is there anything else I should do?
This was sent 4 days before you asked:
https://lore.kernel.org/r/20260507152835.GR305027@google.com
Something not working?
--
Lee Jones
next prev parent reply other threads:[~2026-05-13 13:39 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-27 10:49 [PATCH v3 0/4] gpio: timberdale: remove platform data header Bartosz Golaszewski
2026-03-27 10:49 ` [PATCH v3 1/4] mfd: timberdale: move GPIO_NR_PINS into the driver Bartosz Golaszewski
2026-03-27 11:02 ` Andy Shevchenko
2026-04-09 12:51 ` Lee Jones
2026-04-09 13:18 ` (subset) " Lee Jones
2026-04-09 13:20 ` Lee Jones
2026-04-09 13:21 ` Bartosz Golaszewski
2026-04-09 13:45 ` Lee Jones
2026-03-27 10:49 ` [PATCH v3 2/4] mfd: timberdale: set up a software node for the GPIO cell Bartosz Golaszewski
2026-04-30 9:48 ` (subset) " Lee Jones
2026-04-30 9:53 ` Lee Jones
2026-03-27 10:49 ` [PATCH v3 3/4] gpio: timberdale: use device properties Bartosz Golaszewski
2026-03-27 10:49 ` [PATCH v3 4/4] gpio: timberdale: remove platform data header Bartosz Golaszewski
2026-04-09 13:21 ` [PATCH v3 0/4] " Lee Jones
2026-04-30 9:48 ` Lee Jones
2026-04-30 9:52 ` Lee Jones
2026-05-11 7:34 ` Bartosz Golaszewski
2026-05-13 13:39 ` Lee Jones [this message]
2026-05-13 13:44 ` Bartosz Golaszewski
2026-05-07 15:28 ` [GIT PULL] Immutable branch between MFD and GPIO due for the v7.2 merge window Lee Jones
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=20260513133950.GX305027@google.com \
--to=lee@kernel.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bartosz.golaszewski@oss.qualcomm.com \
--cc=brgl@kernel.org \
--cc=linusw@kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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