From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: Last call for new machine support
Date: Mon, 18 Oct 2010 18:46:32 -0700 [thread overview]
Message-ID: <20101019014632.GO13341@atomide.com> (raw)
In-Reply-To: <20101018211119.GB20376@n2100.arm.linux.org.uk>
* Russell King - ARM Linux <linux@arm.linux.org.uk> [101018 14:12]:
> Tuesday evening my time (BST, so UTC+1h) is the last time I'm merging
> anything into my git tree.
>
> With the upcoming change to the debug macro infrastructure, there are
> two options for people who have new board support code external to my
> tree:
>
> 1. Send me a pull request (based on Linus' tree not mine) by Tuesday.
>
> 2. Eat merge conflicts and build breakage for breakfast when my tree
> merges into mainline. ;)
>
> No further complaints about this please - there's been plenty of warning
> about these debug macro changes.
Omap tree is ready to go and has been tested with these changes,
and we've already set up things for option #2 above. So as far
as omap is concerned, let's get these patches merged!
Tony
prev parent reply other threads:[~2010-10-19 1:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-18 21:11 Last call for new machine support Russell King - ARM Linux
2010-10-18 23:36 ` Kukjin Kim
2010-10-19 1:46 ` Tony Lindgren [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=20101019014632.GO13341@atomide.com \
--to=tony@atomide.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 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.