linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: John Linn <John.Linn@xilinx.com>
To: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Grant Likely <grant.likely@secretlab.ca>
Subject: xilinx linux-next tree addition request
Date: Fri, 25 Mar 2011 14:35:12 -0600	[thread overview]
Message-ID: <58f8b399-ac49-484c-9e99-d23bcda08a8b@VA3EHSMHS024.ehs.local> (raw)

Hi Stephen,

I have a tree I'd like to see show up in linux-next: 

git://git.xilinx.com/linux-2.6-xlnx.git arm-next 

After v2.6.39-rc1 is released, it will contain Xilinx ARM work intended
for the 2.6.40 merge window.  Everything in there has been posted,
reviewed, fixed, etc...

If order makes a difference, it would be best if it's after Russell's
tree as it could have dependencies on stuff in his tree.

It is only Linus's linux-2.6 tree right now, but I wanted to get this
all staged up and ready.

Thanks,
John   





This email and any attachments are intended for the sole use of the named recipient(s) and contain(s) confidential information that may be proprietary, privileged or copyrighted under applicable law. If you are not the intended recipient, do not read, copy, or forward this email message or any attachments. Delete this email message and any attachments immediately.

             reply	other threads:[~2011-03-25 20:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-25 20:35 John Linn [this message]
2011-03-29 23:13 ` xilinx linux-next tree addition request Stephen Rothwell
2011-03-29 23:18   ` John Linn

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=58f8b399-ac49-484c-9e99-d23bcda08a8b@VA3EHSMHS024.ehs.local \
    --to=john.linn@xilinx.com \
    --cc=grant.likely@secretlab.ca \
    --cc=linux-kernel@vger.kernel.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 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).