public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Andrea della Porta <andrea.porta@suse.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Florian Fainelli <florian.fainelli@broadcom.com>,
	soc@kernel.org, Andrea della Porta <andrea.porta@suse.com>,
	Linus Walleij <linus.walleij@linaro.org>,
	"Bjorn Helgaas # quirks . c" <bhelgaas@google.com>,
	pci_ids.h@broadcom.com, Stefan Wahren <wahrenst@gmx.net>,
	Randy Dunlap # build-tested <rdunlap@infradead.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
	linux-arm-kernel@lists.infradead.org, arnd@arndb.de,
	khilman@kernel.org, bcm-kernel-feedback-list@broadcom.com
Subject: Re: [GIT PULL 4/5] Broadcom drivers changes for 6.17
Date: Tue, 1 Jul 2025 12:11:31 +0200	[thread overview]
Message-ID: <aGO0U5yuEZkIZev0@apocalypse> (raw)
In-Reply-To: <2025070139-garnish-leotard-9824@gregkh>

Hi Greg,

On 07:11 Tue 01 Jul     , Greg Kroah-Hartman wrote:
> On Mon, Jun 30, 2025 at 12:02:15PM -0700, Florian Fainelli wrote:
> > The following changes since commit 19272b37aa4f83ca52bdf9c16d5d81bdd1354494:
> > 
> >   Linux 6.16-rc1 (2025-06-08 13:44:43 -0700)
> > 
> > are available in the Git repository at:
> > 
> >   https://github.com/Broadcom/stblinux.git tags/arm-soc/for-6.17/drivers
> > 
> > for you to fetch changes up to e3ce7b897388339b407d57969acaa26063e38209:
> > 
> >   pinctrl: rp1: Implement RaspberryPi RP1 pinmux/pinconf support (2025-06-25 12:08:56 -0700)
> > 
> > ----------------------------------------------------------------
> > This pull request contains Broadcom SoCs drivers updates for 6.17,
> > please pull the following:
> > 
> > - Andrea adds the RP1 clock, pinctrl/pinconf/gpio and misc driver to
> >   bind them all
> > 
> > ----------------------------------------------------------------
> > Andrea della Porta (5):
> >       dt-bindings: clock: Add RaspberryPi RP1 clock bindings
> >       clk: rp1: Add support for clocks provided by RP1
> >       pinctrl: rp1: Implement RaspberryPi RP1 gpio support
> >       misc: rp1: RaspberryPi RP1 misc driver
> >       pinctrl: rp1: Implement RaspberryPi RP1 pinmux/pinconf support
> > 
> >  .../bindings/clock/raspberrypi,rp1-clocks.yaml     |   58 +
> >  drivers/clk/Kconfig                                |    9 +
> >  drivers/clk/Makefile                               |    1 +
> >  drivers/clk/clk-rp1.c                              | 1494 ++++++++++++++++
> >  drivers/misc/Kconfig                               |    1 +
> >  drivers/misc/Makefile                              |    1 +
> >  drivers/misc/rp1/Kconfig                           |   20 +
> >  drivers/misc/rp1/Makefile                          |    3 +
> >  drivers/misc/rp1/rp1-pci.dtso                      |   25 +
> >  drivers/misc/rp1/rp1_pci.c                         |  333 ++++
> 
> Any chance to actually review this code before you throw it under a
> different maintainer's responsibility?
> 
> And what's wrong with patches, why a pull request here?

Since the patchset is spanning several subsystems and some file
dependencies were shared between maintainers, Florian was so kind
to funnell all patches through the Broadcom tree, as the following
mail explains:

https://lore.kernel.org/all/0e154ae3-e0ab-4a4e-aa39-999ea1c720ed@broadcom.com/

Let me summarize the patch history here below:

dt-bindings: clock: Add RaspberryPi RP1 clock bindings - 
	Reviewed-by: Krzysztof and Florian [1,2]

clk: rp1: Add support for clocks provided by RP1 - 
	Stephen: [3]

pinctrl: rp1: Implement RaspberryPi RP1 gpio support - 
	Reviewed-by: Linus W. and Stefan W. [4,5]

misc: rp1: RaspberryPi RP1 misc driver -
	Acked-by: Bjorn H. and Greg [6,7]

pinctrl: rp1: Implement RaspberryPi RP1 pinmux/pinconf support -
	Acked-by: Linus W. [8]

Regarding the testing phase, I and some colleagues at SUSE have tested
the patchset from quite some time now.

Links:
[1] - https://lore.kernel.org/all/leeeqocyjme2sbjbwsw6whisyu6aeq7vfypdi4arktpowzxvek@ejjyxx4iliap/
[2] - https://lore.kernel.org/all/a70e8c45-97a8-4fb6-9b27-4f9ed020211c@broadcom.com/
[3] - https://lore.kernel.org/all/8513c30f597f757a199e4f9a565b0bf5@kernel.org/
[4] - https://lore.kernel.org/all/CACRpkdZCbvNY=B05e9wGqNr5b4t8GrDVsr01C3xd5E-WWwPyMQ@mail.gmail.com/
[5] - https://lore.kernel.org/all/0c6fa2cc-3a7e-4db2-bbad-7c19a876937e@gmx.net/
[6] - https://lore.kernel.org/all/20250416193152.GA78446@bhelgaas/
[7] - https://lore.kernel.org/all/2025042551-agency-boozy-dc3b@gregkh/
[8] - https://lore.kernel.org/all/CACRpkdbAxyZK_f8y6mzX_eJ3UM5ZtuXEpSmXE+QpUXaHKw_NGg@mail.gmail.com/

Many thanks,
Andrea

> 
> thanks,
> 
> greg k-h


  reply	other threads:[~2025-07-01 10:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-30 19:02 [GIT PULL 1/5] Broadcom defconfig-arm64 changes for 6.17 Florian Fainelli
2025-06-30 19:02 ` [GIT PULL 2/5] Broadcom devicetree " Florian Fainelli
2025-06-30 19:02 ` [GIT PULL 3/5] Broadcom devicetree-arm64 " Florian Fainelli
2025-06-30 19:02 ` [GIT PULL 4/5] Broadcom drivers " Florian Fainelli
2025-07-01  5:11   ` Greg Kroah-Hartman
2025-07-01 10:11     ` Andrea della Porta [this message]
2025-06-30 19:02 ` [GIT PULL 5/5] Broadcom maintainers " Florian Fainelli

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=aGO0U5yuEZkIZev0@apocalypse \
    --to=andrea.porta@suse.com \
    --cc=arnd@arndb.de \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=bhelgaas@google.com \
    --cc=florian.fainelli@broadcom.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=khilman@kernel.org \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=pci_ids.h@broadcom.com \
    --cc=rdunlap@infradead.org \
    --cc=soc@kernel.org \
    --cc=wahrenst@gmx.net \
    /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