From: Simon Horman <horms@verge.net.au>
To: linux-arm-kernel@lists.infradead.org
Subject: New Renesas Tree
Date: Mon, 27 Aug 2012 09:08:51 +0000 [thread overview]
Message-ID: <20120827090851.GK29274@verge.net.au> (raw)
Hi,
I am in the process of taking over the maintenance work that Rafael Wysocki
was previously handling through his renesas tree. That is basically the ARM
side of things for Renesas. As such I have created my own renesas tree:
git://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas.git
The basic structure that I am aiming for is to have topic-branches that
I will request that the arm-soc team pull. And a merge-branch next, which
will be frequently rebased to include all pending topic-branches and
should be included in linux-next.
As things stand I have now sifted through the backlog of patches and I have
either queued up or sent an email query about all patches that I could
find. In either case, if you have an outstanding patch for the renesas tree
and you have not received an email from me about it in the past few days
that means that I have missed it, so please repost.
I will endeavour to get all currently queued patches included in 3.7.
reply other threads:[~2012-08-27 9:08 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20120827090851.GK29274@verge.net.au \
--to=horms@verge.net.au \
--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).