From: Tony Lindgren <tony@atomide.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Kalle Valo <kalle.valo@nokia.com>,
linux-omap@vger.kernel.org,
Jani Nikula <ext-jani.1.nikula@nokia.com>
Subject: Re: linux-next: manual merge of the input tree with the omap tree
Date: Fri, 20 Nov 2009 12:53:49 -0800 [thread overview]
Message-ID: <20091120205345.GA5764@atomide.com> (raw)
In-Reply-To: <20091120085858.GE3009@core.coreip.homeip.net>
* Dmitry Torokhov <dmitry.torokhov@gmail.com> [091120 00:59]:
> On Wed, Nov 18, 2009 at 06:53:30PM -0800, Tony Lindgren wrote:
> >
> > Dmitry, could you please drop 5018461a887d58f4601207deeebb7c352c2da20a from
> > your tree now?
> >
>
> Done.
Thanks!
Tony
prev parent reply other threads:[~2009-11-20 20:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-19 2:12 linux-next: manual merge of the input tree with the omap tree Stephen Rothwell
2009-11-19 2:53 ` Tony Lindgren
2009-11-20 8:58 ` Dmitry Torokhov
2009-11-20 20:53 ` 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=20091120205345.GA5764@atomide.com \
--to=tony@atomide.com \
--cc=dmitry.torokhov@gmail.com \
--cc=ext-jani.1.nikula@nokia.com \
--cc=kalle.valo@nokia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox