From: <Claudiu.Beznea@microchip.com>
To: <conor@kernel.org>, <linux-riscv@lists.infradead.org>
Cc: <Conor.Dooley@microchip.com>, <mturquette@baylibre.com>,
<sboyd@kernel.org>, <linux-clk@vger.kernel.org>,
<jassisinghbrar@gmail.com>, <linux-kernel@vger.kernel.org>,
<a.zummo@towertech.it>, <alexandre.belloni@bootlin.com>,
<linux-rtc@vger.kernel.org>, <b-liu@ti.com>,
<gregkh@linuxfoundation.org>, <linux-usb@vger.kernel.org>,
<wsa@kernel.org>, <linux-i2c@vger.kernel.org>,
<Daire.McNamara@microchip.com>
Subject: Re: [PATCH v1 1/5] clk: microchip: convert SOC_MICROCHIP_POLARFIRE to ARCH_MICROCHIP_POLARFIRE
Date: Tue, 14 Mar 2023 14:50:18 +0000 [thread overview]
Message-ID: <a0fb3657-8f8b-565c-ca78-895dd5e8c94b@microchip.com> (raw)
In-Reply-To: <20230309204452.969574-2-conor@kernel.org>
On 09.03.2023 22:44, Conor Dooley wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
>
> From: Conor Dooley <conor.dooley@microchip.com>
>
> As part of converting RISC-V SOC_FOO symbols to ARCH_FOO to match the
> use of such symbols on other architectures, convert the Microchip FPGA
> clock drivers to use the new symbol.
>
> Signed-off-by: Conor Dooley <conor.dooley@microchip.com>
Applied to clk-microchip, thanks!
next prev parent reply other threads:[~2023-03-14 14:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-09 20:44 [PATCH v1 0/5] Convert users of SOC_MICROCHIP_POLARFIRE to ARCH_MICROCHIP_POLARFIRE Conor Dooley
2023-03-09 20:44 ` [PATCH v1 1/5] clk: microchip: convert " Conor Dooley
2023-03-14 14:50 ` Claudiu.Beznea [this message]
2023-03-09 20:44 ` [PATCH v1 2/5] i2c: microchip-core: " Conor Dooley
2023-03-16 19:18 ` Wolfram Sang
2023-03-09 20:44 ` [PATCH v1 3/5] mailbox: mpfs: " Conor Dooley
2023-03-09 20:44 ` [PATCH v1 4/5] rtc: " Conor Dooley
2023-03-17 22:13 ` (subset) " Alexandre Belloni
2023-03-09 20:44 ` [PATCH v1 5/5] usb: musb: " 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=a0fb3657-8f8b-565c-ca78-895dd5e8c94b@microchip.com \
--to=claudiu.beznea@microchip.com \
--cc=Conor.Dooley@microchip.com \
--cc=Daire.McNamara@microchip.com \
--cc=a.zummo@towertech.it \
--cc=alexandre.belloni@bootlin.com \
--cc=b-liu@ti.com \
--cc=conor@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jassisinghbrar@gmail.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-rtc@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=sboyd@kernel.org \
--cc=wsa@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