Linux-RISC-V Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Conor Dooley <conor@kernel.org>
To: paul.walmsley@sifive.com, palmer@dabbelt.com,
	aou@eecs.berkeley.edu, inochiama@outlook.com, guoren@kernel.org,
	emil.renner.berthing@canonical.com, apatel@ventanamicro.com,
	hal.feng@starfivetech.com, dfustini@baylibre.com,
	prabhakar.mahadev-lad.rj@bp.renesas.com,
	linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
	haijiao.liu@sophgo.com, xiaoguang.xing@sophgo.com,
	Chen Wang <unicornxw@gmail.com>
Cc: conor@kernel.org, Conor Dooley <conor.dooley@microchip.com>,
	Chen Wang <unicorn_wang@outlook.com>
Subject: Re: [PATCH] riscv: defconfig: sophgo: enable clks for sg2042
Date: Mon, 19 Aug 2024 18:02:37 +0100	[thread overview]
Message-ID: <20240819-calibrate-playpen-964bfa720a3b@spud> (raw)
In-Reply-To: <20240805023320.1287061-1-unicornxw@gmail.com>

From: Conor Dooley <conor.dooley@microchip.com>

On Mon, 05 Aug 2024 10:33:20 +0800, Chen Wang wrote:
> Enable clk generators for sg2042 due to many peripherals rely on
> these clocks.
> 
> 

Applied to riscv-config-for-next, thanks!

[1/1] riscv: defconfig: sophgo: enable clks for sg2042
      https://git.kernel.org/conor/c/3ccedd259cc3

Thanks,
Conor.

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

  parent reply	other threads:[~2024-08-19 17:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-05  2:33 [PATCH] riscv: defconfig: sophgo: enable clks for sg2042 Chen Wang
2024-08-06  9:30 ` Emil Renner Berthing
2024-08-07  0:45   ` Chen Wang
2024-08-09  6:26 ` Chen Wang
2024-08-15  0:09   ` Chen Wang
2024-08-19 17:02 ` Conor Dooley [this message]
2024-08-19 23:49   ` Chen Wang

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=20240819-calibrate-playpen-964bfa720a3b@spud \
    --to=conor@kernel.org \
    --cc=aou@eecs.berkeley.edu \
    --cc=apatel@ventanamicro.com \
    --cc=conor.dooley@microchip.com \
    --cc=dfustini@baylibre.com \
    --cc=emil.renner.berthing@canonical.com \
    --cc=guoren@kernel.org \
    --cc=haijiao.liu@sophgo.com \
    --cc=hal.feng@starfivetech.com \
    --cc=inochiama@outlook.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@sifive.com \
    --cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
    --cc=unicorn_wang@outlook.com \
    --cc=unicornxw@gmail.com \
    --cc=xiaoguang.xing@sophgo.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