From: Stephen Boyd <sboyd@kernel.org>
To: Florian Fainelli <florian.fainelli@broadcom.com>,
linux-arm-kernel@lists.infradead.org
Cc: Florian Fainelli <florian.fainelli@broadcom.com>,
Michael Turquette <mturquette@baylibre.com>,
Jassi Brar <jassisinghbrar@gmail.com>,
Bjorn Andersson <quic_bjorande@quicinc.com>,
Maximilian Luz <luzmaximilian@gmail.com>,
Ard Biesheuvel <ardb@kernel.org>,
Johan Hovold <johan+linaro@kernel.org>,
Michael S. Tsirkin <mst@redhat.com>,
Sudeep Holla <sudeep.holla@arm.com>,
Conor Dooley <conor.dooley@microchip.com>,
Bartosz Golaszewski <bartosz.golaszewski@linaro.org>,
linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org,
Stefan Wahren <wahrenst@gmx.net>
Subject: Re: [PATCH 3/3] clk: bcm: Make CLK_RASPBERRYPI default to RASPBERRYPI_FIRMWARE
Date: Tue, 14 May 2024 14:06:45 -0700 [thread overview]
Message-ID: <4dcf39c7c2f30acc38fd245883f62dd2.sboyd@kernel.org> (raw)
In-Reply-To: <20240513235234.1474619-4-florian.fainelli@broadcom.com>
Quoting Florian Fainelli (2024-05-13 16:52:34)
> The clock driver is essential in providing clocks for UARTs and other
> peripherals, make it enabled by default.
>
> Signed-off-by: Florian Fainelli <florian.fainelli@broadcom.com>
> ---
Acked-by: Stephen Boyd <sboyd@kernel.org>
prev parent reply other threads:[~2024-05-14 21:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-13 23:52 [PATCH 0/3] ARCH_BCM2835 Kconfig changes Florian Fainelli
2024-05-13 23:52 ` [PATCH 1/3] mailbox: Make BCM2835_MBOX default to ARCH_BCM2835 Florian Fainelli
2024-05-14 12:29 ` Conor Dooley
2024-05-14 16:20 ` Florian Fainelli
2024-05-15 7:54 ` Conor Dooley
2024-05-31 21:36 ` Florian Fainelli
2024-05-13 23:52 ` [PATCH 2/3] firmware: Default RASPBERRYPI_FIRMWARE " Florian Fainelli
2024-05-13 23:52 ` [PATCH 3/3] clk: bcm: Make CLK_RASPBERRYPI default to RASPBERRYPI_FIRMWARE Florian Fainelli
2024-05-14 21:06 ` Stephen Boyd [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=4dcf39c7c2f30acc38fd245883f62dd2.sboyd@kernel.org \
--to=sboyd@kernel.org \
--cc=ardb@kernel.org \
--cc=bartosz.golaszewski@linaro.org \
--cc=conor.dooley@microchip.com \
--cc=florian.fainelli@broadcom.com \
--cc=jassisinghbrar@gmail.com \
--cc=johan+linaro@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luzmaximilian@gmail.com \
--cc=mst@redhat.com \
--cc=mturquette@baylibre.com \
--cc=quic_bjorande@quicinc.com \
--cc=sudeep.holla@arm.com \
--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