From: Kevin Hilman <khilman@deeprootsystems.com>
To: Russell King <rmk@arm.linux.org.uk>, Tony Lindgren <tony@atomide.com>
Cc: linux-omap@vger.kernel.org
Subject: OMAP submissions for next merge window
Date: Wed, 10 Jun 2009 07:25:21 -0700 [thread overview]
Message-ID: <87ab4gupwu.fsf@deeprootsystems.com> (raw)
Russell,
For this merge window, we submitted multiple changesets for OMAP which
Tony then queued up in his for-next branch. In some offline
discussions, you suggested for the next window we might try a slightly
different approach. You expressed a preference for merging each
series directly into your tree after review. Can you confirm and/or
clarify your preference here?
Thanks,
Kevin
reply other threads:[~2009-06-10 14:25 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=87ab4gupwu.fsf@deeprootsystems.com \
--to=khilman@deeprootsystems.com \
--cc=linux-omap@vger.kernel.org \
--cc=rmk@arm.linux.org.uk \
--cc=tony@atomide.com \
/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