Linux SpacemiT device drivers
 help / color / mirror / Atom feed
From: Yixun Lan <dlan@kernel.org>
To: linux-next@vger.kernel.org
Cc: Mark Brown <broonie@kernel.org>,
	soc@kernel.org, spacemit@lists.linux.dev
Subject: Include in next: Switch SpacemiT SoC tree's repo
Date: Wed, 1 Jul 2026 00:15:06 +0000	[thread overview]
Message-ID: <20260701001506-GKA20854@kernel.org> (raw)

Hi Linux-Next Maintainer,

  Previously, the SpacemiT SoC tree was hosted in github.com[1],
while now we've created a new kernel tree at kernel.org[2],
so please help to update the repo url for linux-next tree to the
new one, and the other info should being unchanged, that's:
  branch for master: for-next
  branch for pending-fixes: fixes
 
  I will also switch to new repo for sending next Pull-Request to
SoC tree maintainer.

  Thank you

[1] https://github.com/spacemit-com/linux
[2] https://git.kernel.org/pub/scm/linux/kernel/git/spacemit/linux.git/

-- 
Yixun Lan (dlan)

             reply	other threads:[~2026-07-01  0:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-01  0:15 Yixun Lan [this message]
2026-07-01 15:47 ` Include in next: Switch SpacemiT SoC tree's repo Mark Brown

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=20260701001506-GKA20854@kernel.org \
    --to=dlan@kernel.org \
    --cc=broonie@kernel.org \
    --cc=linux-next@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox