From: Stephen Boyd <sboyd@kernel.org>
To: Conor Dooley <conor.dooley@microchip.com>,
Conor Dooley <conor@kernel.org>
Cc: Conor Dooley <conor.dooley@microchip.com>,
linux-clk@vger.kernel.org, daire.mcnamara@microchip.com,
linux-riscv@lists.infradead.org
Subject: Re: [PATCH] MAINTAINERS: add missing clock driver coverage for Microchip FPGAs
Date: Mon, 06 Mar 2023 12:17:53 -0800 [thread overview]
Message-ID: <aeb088d8b7bec8929c7c9e9539a0b187.sboyd@kernel.org> (raw)
In-Reply-To: <20230222124610.257101-1-conor.dooley@microchip.com>
Quoting Conor Dooley (2023-02-22 04:46:11)
> When the CCC support was added, the clock binding coverage was
> converted to a regex in commit 71c8517e004b ("MAINTAINERS: update
> polarfire soc clock binding"), but the coverage for the clock drivers
> themselves was not updated. Rectify that now.
>
> Signed-off-by: Conor Dooley <conor.dooley@microchip.com>
> ---
Applied to clk-fixes
prev parent reply other threads:[~2023-03-06 20:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-22 12:46 [PATCH] MAINTAINERS: add missing clock driver coverage for Microchip FPGAs Conor Dooley
2023-03-06 20:17 ` 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=aeb088d8b7bec8929c7c9e9539a0b187.sboyd@kernel.org \
--to=sboyd@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=conor@kernel.org \
--cc=daire.mcnamara@microchip.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-riscv@lists.infradead.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