From: Stephen Boyd <sboyd@kernel.org>
To: Michael Turquette <mturquette@baylibre.com>,
Stefan Wahren <stefan.wahren@i2se.com>
Cc: bcm-kernel-feedback-list@broadcom.com,
Maxime Ripard <maxime@cerno.tech>,
linux-clk@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Florian Fainelli <f.fainelli@gmail.com>,
Ivan T. Ivanov <iivanov@suse.de>
Subject: Re: [PATCH 0/3] clk: bcm: rpi: Fixes and improvement
Date: Tue, 23 Aug 2022 15:50:22 -0700 [thread overview]
Message-ID: <20220823225024.E528AC433D6@smtp.kernel.org> (raw)
In-Reply-To: <2ecf22d4-3b46-4469-28af-e26f44cf2952@i2se.com>
Quoting Stefan Wahren (2022-08-15 11:15:56)
> Hi Stephen,
>
> Am 04.08.22 um 19:58 schrieb Florian Fainelli:
> > On 7/25/22 01:18, Ivan T. Ivanov wrote:
> >> Hi,
> >>
> >> On 07-13 17:49, Stefan Wahren wrote:
> >>> This series tries to fix and improvement the Raspberry Pi firmware clock
> >>> driver. This mostly focus on clock discovery mechanism.
> >>>
> >>> Just a note patch #3 depends on patch #2.
> >>>
> >>> Stefan Wahren (3):
> >>> clk: bcm: rpi: Prevent out-of-bounds access
> >>> clk: bcm: rpi: Add missing newline
> >>> clk: bcm: rpi: Show clock id limit in error case
> >>>
> >> Maybe is little bit late, but still :-)
> >>
> >> Reviewed-by: Ivan T. Ivanov <iivanov@suse.de>
> > Stephen, can you apply those patches? Thanks!
>
> should i resend this series?
>
No. Thanks!
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2022-08-23 22:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-13 15:49 [PATCH 0/3] clk: bcm: rpi: Fixes and improvement Stefan Wahren
2022-07-13 15:49 ` [PATCH 1/3] clk: bcm: rpi: Prevent out-of-bounds access Stefan Wahren
2022-07-13 16:25 ` Florian Fainelli
2022-08-23 22:52 ` Stephen Boyd
2022-07-13 15:49 ` [PATCH 2/3] clk: bcm: rpi: Add missing newline Stefan Wahren
2022-07-13 16:26 ` Florian Fainelli
2022-08-23 22:51 ` Stephen Boyd
2022-07-13 15:49 ` [PATCH 3/3] clk: bcm: rpi: Show clock id limit in error case Stefan Wahren
2022-07-13 16:33 ` Florian Fainelli
2022-08-23 22:51 ` Stephen Boyd
2022-07-25 8:18 ` [PATCH 0/3] clk: bcm: rpi: Fixes and improvement Ivan T. Ivanov
2022-08-04 17:58 ` Florian Fainelli
2022-08-15 18:15 ` Stefan Wahren
2022-08-23 22:50 ` 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=20220823225024.E528AC433D6@smtp.kernel.org \
--to=sboyd@kernel.org \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=f.fainelli@gmail.com \
--cc=iivanov@suse.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maxime@cerno.tech \
--cc=mturquette@baylibre.com \
--cc=stefan.wahren@i2se.com \
/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 NNTP newsgroup(s).