From: ryan@bluewatersys.com (Ryan Mallon)
To: linux-arm-kernel@lists.infradead.org
Subject: EP93XX and TS-72XX
Date: Thu, 01 Oct 2009 09:32:59 +1300 [thread overview]
Message-ID: <4AC3C07B.80407@bluewatersys.com> (raw)
In-Reply-To: <4AC3B1AA.6000100@techworks.ie>
Christian Gagneraud wrote:
> Hi all,
>
> I saw that there's things on going for the EP93XX, i would like to
> contribute by testing and submitting patch for EP93XX and TS-72XX
> boards. There's lot of patches maintained by some peoples around.
Excellent.
> Which git tree should I use to prepare and test patches? SFR's
> linux-next or RMK's one?
> I saw on the path tracker that the last path was submitted on the 25th
> and its status is "incoming" for version 2.6.31-git16 and the last
> submited patch is for 2.6.32-rc2.
You can just base your patches on Linus' latest tree.
~Ryan
--
Bluewater Systems Ltd - ARM Technology Solution Centre
Ryan Mallon 5 Amuri Park, 404 Barbadoes St
ryan at bluewatersys.com PO Box 13 889, Christchurch 8013
http://www.bluewatersys.com New Zealand
Phone: +64 3 3779127 Freecall: Australia 1800 148 751
Fax: +64 3 3779135 USA 1800 261 2934
prev parent reply other threads:[~2009-09-30 20:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-30 19:29 EP93XX and TS-72XX Christian Gagneraud
2009-09-30 20:32 ` Ryan Mallon [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=4AC3C07B.80407@bluewatersys.com \
--to=ryan@bluewatersys.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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).