From: Paul Mundt <lethal@linux-sh.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Russell King <rmk@arm.linux.org.uk>, linux-next@vger.kernel.org
Subject: genesis-2.6 tree addition request
Date: Mon, 8 Feb 2010 13:32:09 +0900 [thread overview]
Message-ID: <20100208043209.GA7674@linux-sh.org> (raw)
I'd like to get the genesis-2.6 tree rolled in to -next. This is
primarily for supporting ARM-based SH-Mobile G-series CPUs, which were
previously discussed on the ARM lists.
There shouldn't be any ordering issues, but it would be ideal to place
this after both the sh and arm trees in the merge order to avoid any
future issues.
The tree is at:
git://git.kernel.org/pub/scm/linux/kernel/git/lethal/genesis-2.6.git
and also contains the following defconfigs:
ap4evb_defconfig
g3evm_defconfig
g4evm_defconfig
which would be nice to have added to the ARM defconfig builds. Any issues
that pop up with these configs are likely to be SH-related and ideally
should come to me directly, rather than having to bother Russell with
them.
next reply other threads:[~2010-02-08 4:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-08 4:32 Paul Mundt [this message]
2010-02-08 7:40 ` genesis-2.6 tree addition request 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=20100208043209.GA7674@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=linux-next@vger.kernel.org \
--cc=rmk@arm.linux.org.uk \
--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.