All of lore.kernel.org
 help / color / mirror / Atom feed
From: Florian Mickler <florian@mickler.org>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
	Dave Airlie <airlied@gmail.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	LKML <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>,
	Keith Packard <keithp@keithp.com>
Subject: Re: "do_IRQ: 0.89 No irq handler for vector (irq -1)"
Date: Tue, 16 Nov 2010 21:47:26 +0100	[thread overview]
Message-ID: <20101116214726.440e9846@schatten.dmk.lab> (raw)
In-Reply-To: <20101116121107.7728e971@jbarnes-desktop>

On Tue, 16 Nov 2010 12:11:07 -0800
Jesse Barnes <jbarnes@virtuousgeek.org> wrote:

> On Tue, 16 Nov 2010 20:46:45 +0100
> Florian Mickler <florian@mickler.org> wrote:
> 
> > On Tue, 12 Oct 2010 12:49:38 -0700
> > Jesse Barnes <jbarnes@virtuousgeek.org> wrote:
> > > I don't think I buy that VGA is special anyway, at least not for KMS
> > > enabled kernels, where vgacon and the BIOS can't assume anything about
> > > graphics state anymore.  More generally, I don't think BIOSes have been
> > > able to assume anything about the current graphics state since Windows
> > > 3.1, when most platforms stopped using BIOS calls and/or VGA regs for
> > > mode setting.
> > > 
> > > Thoughts?
> > > 
> > 
> > does this need to go to 2.6.36.y? (is it already on it's way?)
> > 
> > commit 97c145f7c87453cec90e91238fba5fe2c1561b32
> > Author: Jesse Barnes <jbarnes@virtuousgeek.org>
> > Date:   Fri Nov 5 15:16:36 2010 -0400
> > 
> >     PCI: read current power state at enable time
> 
> I hadn't planned on pushing this to stable, but if you have a need
> for it there, feel free to propose it.
> 
No, I don't need it. I was closing a regression tracker and thought I
should check. You can judge the impact better then me. 

Regards,
Flo

  reply	other threads:[~2010-11-16 20:47 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-07  8:55 "do_IRQ: 0.89 No irq handler for vector (irq -1)" Dave Airlie
2010-10-07  9:05 ` Dave Airlie
2010-10-07 20:38 ` Thomas Gleixner
2010-10-07 21:35   ` Thomas Gleixner
2010-10-08  7:52     ` Thomas Gleixner
2010-10-08 11:46       ` Dave Airlie
2010-10-11 22:48         ` Jesse Barnes
2010-10-11 23:40           ` Jesse Barnes
2010-10-12 19:01             ` Rafael J. Wysocki
2010-10-12 19:49               ` Jesse Barnes
2010-11-16 19:46                 ` Florian Mickler
2010-11-16 20:11                   ` Jesse Barnes
2010-11-16 20:47                     ` Florian Mickler [this message]
2010-10-13 21:20               ` Jesse Barnes
2010-10-13 21:48                 ` Rafael J. Wysocki
2010-10-08 11:53     ` Chris Wilson
2010-10-08 12:15       ` Thomas Gleixner
2010-10-08 12:30         ` Chris Wilson
2010-10-10 17:46 ` Maciej Rutecki

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=20101116214726.440e9846@schatten.dmk.lab \
    --to=florian@mickler.org \
    --cc=airlied@gmail.com \
    --cc=jbarnes@virtuousgeek.org \
    --cc=keithp@keithp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rjw@sisk.pl \
    --cc=tglx@linutronix.de \
    /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.