From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for March 24
Date: Wed, 24 Mar 2010 00:29:17 -0700 [thread overview]
Message-ID: <20100324072916.GA4254@core.coreip.homeip.net> (raw)
In-Reply-To: <20100324161746.85edc5a3.sfr@canb.auug.org.au>
On Wed, Mar 24, 2010 at 04:17:46PM +1100, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20100323:
>
> Dropped tree: tmio-mmc (long unresolved conflicts and unable to fetch)
>
> My fixes tree contains:
> a patch for a pktcdvd build error from Arnd Bergmann
> a revert of the commit that broke virtual consoles on PowerPC
>
> The input tree still has its build failure for which I reverted a commit.
>
Should be fixed now.
--
Dmitry
next prev parent reply other threads:[~2010-03-24 7:29 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-24 5:17 linux-next: Tree for March 24 Stephen Rothwell
2010-03-24 7:29 ` Dmitry Torokhov [this message]
2010-03-24 19:44 ` linux-next: Tree for March 24 (staging/vt66*) Randy Dunlap
2010-03-25 13:00 ` Forest Bond
2010-03-25 15:38 ` Randy Dunlap
2010-04-17 15:03 ` [PATCH] vt6656: Rename hostap_set_hostapd, hostap_iotctl Forest Bond
2010-04-17 15:03 ` [PATCH] vt6655: " Forest Bond
2010-03-24 20:19 ` linux-next: Tree for March 24 (iwlwifi) Randy Dunlap
2010-03-24 21:23 ` [PATCH] iwlwifi: fix build error for CONFIG_IWLAGN=n John W. Linville
[not found] ` <1269465799-19060-1-git-send-email-linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
2010-03-24 21:33 ` Johannes Berg
2010-03-24 21:42 ` reinette chatre
2010-03-24 22:37 ` John W. Linville
2010-03-24 22:41 ` reinette chatre
2010-03-24 23:38 ` John W. Linville
2010-03-25 16:33 ` reinette chatre
2010-03-24 22:59 ` Randy Dunlap
-- strict thread matches above, loose matches on Subject: below --
2011-03-24 3:47 linux-next: Tree for March 24 Stephen Rothwell
2009-03-24 7:30 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=20100324072916.GA4254@core.coreip.homeip.net \
--to=dmitry.torokhov@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@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;
as well as URLs for NNTP newsgroup(s).