From: Chris Zankel <chris@zankel.net>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, Max Filippov <jcmvbkbc@gmail.com>
Subject: Re: Resurrecting linux-next tree for Xtensa
Date: Thu, 09 Aug 2012 16:04:23 -0700 [thread overview]
Message-ID: <502441F7.2060208@zankel.net> (raw)
In-Reply-To: <20120810085312.bb2f1df59f6f4dfdca965de1@canb.auug.org.au>
Hi Stephen,
On 08/09/2012 03:53 PM, Stephen Rothwell wrote:
> Hi Chris.
>
> On Wed, 08 Aug 2012 20:24:07 -0700 Chris Zankel <chris@zankel.net> wrote:
>> I was wondering and hoping you could add the Xtensa 'next' tree back to
>> the linux-next tree?
>>
>> It's currently on github (at least, until I get my access back to
>> kernel.org)
> You will need to get a gpg key signed so that you can move this tree to
> kernel.org or to signed tags when you ask Linus to pull your tree.
Working on it...
>> git://github.com/czankel/xtensa-linux.git#for-next
> ^
> I used "for_next". Just to be sure, that branch is currently empty,
> right?
Correct. Patches should be popping up in a few days...
>> It's been outdated for some time now and with more help we want to bring
>> it up-to-date again.
> Sounds like a good plan!
>
> Thanks for adding your subsystem tree as a participant of linux-next. As
I appreciate all the time and effort you put into the linux-next tree!
Thanks so much!
Cheers!
-Chris
prev parent reply other threads:[~2012-08-09 23:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-09 3:24 Resurrecting linux-next tree for Xtensa Chris Zankel
2012-08-09 22:53 ` Stephen Rothwell
2012-08-09 23:04 ` Chris Zankel [this message]
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=502441F7.2060208@zankel.net \
--to=chris@zankel.net \
--cc=jcmvbkbc@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).