All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yixun Lan <dlan@kernel.org>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: soc@kernel.org, Arnd Bergmann <arnd@arndb.de>,
	spacemit@lists.linux.dev, linux-riscv@lists.infradead.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] RISC-V SpacemiT Devicetrees for v7.2
Date: Tue, 9 Jun 2026 13:25:20 +0000	[thread overview]
Message-ID: <20260609132520-GKE3727415@kernel.org> (raw)
In-Reply-To: <20260609-pompous-imposing-dragon-fc18cb@quoll>

Hi Krzysztof, 

On 14:00 Tue 09 Jun     , Krzysztof Kozlowski wrote:
> On Tue, Jun 02, 2026 at 07:10:07AM +0000, Yixun Lan wrote:
> > Hi SoC Maintainers,
> > 
> >    Please pull SpacemiT's DeviceTree changes for v7.2
> > 
> > Yixun Lan
> > 
> > The following changes since commit 254f49634ee16a731174d2ae34bc50bd5f45e731:
> > 
> >   Linux 7.1-rc1 (2026-04-26 14:19:00 -0700)
> > 
> > are available in the Git repository at:
> > 
> >   https://github.com/spacemit-com/linux spacemit-dt-for-7.2-1
> 
> Please switch to kernel.org repo. Github is not really a trusted place
> and you have kernel.org account, so not sure why Github is still there.
> 
Ok, thanks for the reminder, I could do the switch in next merge window

For reason why I still use Github, mainly because I got kernel.org account
after taking the maintainer role, then never change the repo address..

> > 
> > for you to fetch changes up to 793cc54475b49b5b558902b5c13e4bfe66530a50:
> > 
> >   riscv: dts: spacemit: enable PMIC on OrangePi R2S (2026-06-01 06:32:42 +0000)
> > 
> > ----------------------------------------------------------------
> > RISC-V SpacemiT DT changes for 7.2
> 
> Thanks, applied
> 
Thank you!

-- 
Yixun Lan (dlan)

WARNING: multiple messages have this Message-ID (diff)
From: Yixun Lan <dlan@kernel.org>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: soc@kernel.org, Arnd Bergmann <arnd@arndb.de>,
	spacemit@lists.linux.dev, linux-riscv@lists.infradead.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] RISC-V SpacemiT Devicetrees for v7.2
Date: Tue, 9 Jun 2026 13:25:20 +0000	[thread overview]
Message-ID: <20260609132520-GKE3727415@kernel.org> (raw)
In-Reply-To: <20260609-pompous-imposing-dragon-fc18cb@quoll>

Hi Krzysztof, 

On 14:00 Tue 09 Jun     , Krzysztof Kozlowski wrote:
> On Tue, Jun 02, 2026 at 07:10:07AM +0000, Yixun Lan wrote:
> > Hi SoC Maintainers,
> > 
> >    Please pull SpacemiT's DeviceTree changes for v7.2
> > 
> > Yixun Lan
> > 
> > The following changes since commit 254f49634ee16a731174d2ae34bc50bd5f45e731:
> > 
> >   Linux 7.1-rc1 (2026-04-26 14:19:00 -0700)
> > 
> > are available in the Git repository at:
> > 
> >   https://github.com/spacemit-com/linux spacemit-dt-for-7.2-1
> 
> Please switch to kernel.org repo. Github is not really a trusted place
> and you have kernel.org account, so not sure why Github is still there.
> 
Ok, thanks for the reminder, I could do the switch in next merge window

For reason why I still use Github, mainly because I got kernel.org account
after taking the maintainer role, then never change the repo address..

> > 
> > for you to fetch changes up to 793cc54475b49b5b558902b5c13e4bfe66530a50:
> > 
> >   riscv: dts: spacemit: enable PMIC on OrangePi R2S (2026-06-01 06:32:42 +0000)
> > 
> > ----------------------------------------------------------------
> > RISC-V SpacemiT DT changes for 7.2
> 
> Thanks, applied
> 
Thank you!

-- 
Yixun Lan (dlan)

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

  reply	other threads:[~2026-06-09 13:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-02  7:10 [GIT PULL] RISC-V SpacemiT Devicetrees for v7.2 Yixun Lan
2026-06-02  7:10 ` Yixun Lan
2026-06-09 12:00 ` Krzysztof Kozlowski
2026-06-09 12:00   ` Krzysztof Kozlowski
2026-06-09 13:25   ` Yixun Lan [this message]
2026-06-09 13:25     ` Yixun Lan

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=20260609132520-GKE3727415@kernel.org \
    --to=dlan@kernel.org \
    --cc=arnd@arndb.de \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=soc@kernel.org \
    --cc=spacemit@lists.linux.dev \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.