From: Hector Martin <marcan@marcan.st>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Asahi Linux <asahi@lists.linux.dev>, LKML <linux-kernel@vger.kernel.org>
Subject: Please add asahi-soc to linux-next
Date: Thu, 22 Sep 2022 23:29:29 +0900 [thread overview]
Message-ID: <2159b672-4db7-5add-8046-ed5354dd5343@marcan.st> (raw)
Hi Stephen,
Could you add the asahi-soc trees to linux-next? We are downstream from
SoC and would benefit from testing in linux-next before I send out PRs.
URLs:
https://github.com/AsahiLinux/linux.git asahi-soc/fixes
https://github.com/AsahiLinux/linux.git asahi-soc/for-next
(Right now we have no fixes, and some DT changes in for-next)
Thanks!
- Hector
next reply other threads:[~2022-09-22 14:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-22 14:29 Hector Martin [this message]
2022-09-22 22:19 ` Stephen Rothwell
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=2159b672-4db7-5add-8046-ed5354dd5343@marcan.st \
--to=marcan@marcan.st \
--cc=asahi@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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
all inboxes | Powered by JetHome®