From: Stephen Boyd <sboyd@kernel.org>
To: Conor Dooley <mail@conchuod.ie>,
Palmer Dabbelt <palmer@rivosinc.com>,
atulkhare@rivosinc.com
Cc: mturquette@baylibre.com, aou@eecs.berkeley.edu,
Paul Walmsley <paul.walmsley@sifive.com>,
a.zummo@towertech.it, alexandre.belloni@bootlin.com,
robh+dt@kernel.org, krzk+dt@kernel.org,
daire.mcnamara@microchip.com, linux-rtc@vger.kernel.org,
devicetree@vger.kernel.org, linux-clk@vger.kernel.org,
linux-riscv@lists.infradead.org, conor.dooley@microchip.com
Subject: Re: [PATCH v3 0/9] More PolarFire SoC Fixes for 5.18
Date: Fri, 22 Apr 2022 14:00:38 -0700 [thread overview]
Message-ID: <20220422210040.68019C385AA@smtp.kernel.org> (raw)
In-Reply-To: <0f99ec7b-0c2f-cf6c-162d-af615eb73373@conchuod.ie>
Quoting Conor Dooley (2022-04-22 12:59:09)
> On 22/04/2022 20:39, Palmer Dabbelt wrote:
> >
> > Thanks. These generally look good to me, but I don't see acks from everyone. I'm perfectly fine treating these as fixes and taking them through the RISC-V tree, but looks like it's mostly clk stuff so
> >
> > Acked-by: Palmer Dabbelt <palmer@rivosinc.com>
>
> Ye, hopefully they go via clk. Stephen replied to v1 or 2 so
> I figure they're in his queue :)
It helps to be explicit in the cover letter. It's in my queue but I put
it on hold because the cover letter didn't clarify what tree it was
intended for nor the priority of what is being fixed.
Is boot broken? Do I need to send these up to Linus next week as part of
fixes for this merge window?
next prev parent reply other threads:[~2022-04-22 22:11 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-13 7:58 [PATCH v3 0/9] More PolarFire SoC Fixes for 5.18 Conor Dooley
2022-04-13 7:58 ` [PATCH v3 1/9] clk: microchip: mpfs: fix parents for FIC clocks Conor Dooley
2022-04-23 1:41 ` Stephen Boyd
2022-04-23 17:58 ` Conor Dooley
2022-04-13 7:58 ` [PATCH v3 2/9] clk: microchip: mpfs: mark CLK_ATHENA as critical Conor Dooley
2022-04-23 1:41 ` Stephen Boyd
2022-04-13 7:58 ` [PATCH v3 3/9] riscv: dts: microchip: fix usage of fic clocks on mpfs Conor Dooley
2022-04-23 1:41 ` Stephen Boyd
2022-04-13 7:58 ` [PATCH v3 4/9] dt-bindings: clk: mpfs document msspll dri registers Conor Dooley
2022-04-23 1:41 ` Stephen Boyd
2022-04-13 7:58 ` [PATCH v3 5/9] dt-bindings: clk: mpfs: add defines for two new clocks Conor Dooley
2022-04-19 11:59 ` Krzysztof Kozlowski
2022-04-23 1:41 ` Stephen Boyd
2022-04-13 7:58 ` [PATCH v3 6/9] dt-bindings: rtc: add refclk to mpfs-rtc Conor Dooley
2022-04-23 1:41 ` Stephen Boyd
2022-04-13 7:58 ` [PATCH v3 7/9] clk: microchip: mpfs: re-parent the configurable clocks Conor Dooley
2022-04-23 1:41 ` Stephen Boyd
2022-04-13 7:58 ` [PATCH v3 8/9] clk: microchip: mpfs: add RTCREF clock control Conor Dooley
2022-04-23 1:42 ` Stephen Boyd
2022-04-13 7:58 ` [PATCH v3 9/9] riscv: dts: microchip: reparent mpfs clocks Conor Dooley
2022-04-23 1:42 ` Stephen Boyd
2022-04-22 19:39 ` [PATCH v3 0/9] More PolarFire SoC Fixes for 5.18 Palmer Dabbelt
2022-04-22 19:59 ` Conor Dooley
2022-04-22 21:00 ` Stephen Boyd [this message]
2022-04-22 21:10 ` Conor Dooley
2022-04-22 21:40 ` Palmer Dabbelt
2022-04-22 21:52 ` Rob Herring
2022-04-22 22:32 ` Conor Dooley
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=20220422210040.68019C385AA@smtp.kernel.org \
--to=sboyd@kernel.org \
--cc=a.zummo@towertech.it \
--cc=alexandre.belloni@bootlin.com \
--cc=aou@eecs.berkeley.edu \
--cc=atulkhare@rivosinc.com \
--cc=conor.dooley@microchip.com \
--cc=daire.mcnamara@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-rtc@vger.kernel.org \
--cc=mail@conchuod.ie \
--cc=mturquette@baylibre.com \
--cc=palmer@rivosinc.com \
--cc=paul.walmsley@sifive.com \
--cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).