public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Daniel Drake <dsd@laptop.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	hpa@zytor.com, linux-kernel@vger.kernel.org,
	Andres Salomon <dilinger@queued.net>,
	x86@kernel.org
Subject: Re: OLPC power management patches - merge for 3.1?
Date: Sun, 24 Jul 2011 12:18:10 +0200	[thread overview]
Message-ID: <20110724101810.GA23597@elte.hu> (raw)
In-Reply-To: <CAGq3pz6zGhFCgpeWy2zfWw_fNv2UFz=51uL9cfjArggu=wztcw@mail.gmail.com>


* Daniel Drake <dsd@laptop.org> wrote:

> On 24 July 2011 08:27, Ingo Molnar <mingo@elte.hu> wrote:
> > it's excluded because in testing i found a boot crash with it.
> > Thomas did a quick fix for it but i have not heard about it since
> > then - Thomas/Peter, is this all resolved in x86/olpc?
> 
> Ah, sorry if we broke something. Can you go into more details on the
> crash? We haven't heard anything on these lines. I'm willing to help
> out fixing it.
> 
> Is it related to the apbuart serial patch you included in your mail? I
> don't see how that could have been affected by OLPC patches - but I am
> probably missing something.

i don't have the details anymore, i'll re-test once the build failure 
is fixed. We can certainly push it in this merge window if it's 
stable.

Thanks,

	Ingo

      reply	other threads:[~2011-07-24 10:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-23 22:44 OLPC power management patches - merge for 3.1? Daniel Drake
2011-07-24  3:20 ` Randy Dunlap
2011-07-24  8:59   ` Daniel Drake
2011-07-24 17:13     ` Randy Dunlap
2011-07-24 17:16       ` Daniel Drake
2011-07-24 17:33         ` Randy Dunlap
2011-07-24 17:23       ` Andres Salomon
2011-07-24  7:27 ` Ingo Molnar
2011-07-24  8:55   ` Daniel Drake
2011-07-24 10:18     ` Ingo Molnar [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=20110724101810.GA23597@elte.hu \
    --to=mingo@elte.hu \
    --cc=dilinger@queued.net \
    --cc=dsd@laptop.org \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox