From: Stephen Warren <swarren@wwwdotorg.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>
Subject: Please add bcm2835 tree to linux-next
Date: Thu, 25 Oct 2012 21:02:07 -0600 [thread overview]
Message-ID: <5089FD2F.9090507@wwwdotorg.org> (raw)
StephenR,
Could you please add the bcm2835 ARM SoC tree to linux-next. It's
available at:
git://git.kernel.org/pub/scm/linux/kernel/git/swarren/linux-rpi.git for-next
Its probably best to insert it into the list somewhere after the
existing arm-soc tree. I also maintain the Tegra tree, so if you insert
it right next to that, any issues related to me will be triggered at the
same time:-)
Right now, it's based on v3.7-rc2, plus 5 patches.
Thanks.
next reply other threads:[~2012-10-26 3:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-26 3:02 Stephen Warren [this message]
2012-10-28 23:07 ` Please add bcm2835 tree to linux-next Stephen Rothwell
2012-10-28 23:07 ` 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=5089FD2F.9090507@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=linux-next@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 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.