public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Brownell <david-b@pacbell.net>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: lkml <linux-kernel@vger.kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [patch 2.6.26-rc5] make HPET_RTC_IRQ track HPET_EMULATE_RTC
Date: Sun, 8 Jun 2008 16:05:34 -0700	[thread overview]
Message-ID: <200806081605.35042.david-b@pacbell.net> (raw)
In-Reply-To: <20080608140011.aa3762cd.akpm@linux-foundation.org>

On Sunday 08 June 2008, Andrew Morton wrote:
> On Thu, 5 Jun 2008 22:41:44 -0700 David Brownell <david-b@pacbell.net> wrote:
> 
> > More Kconfig tweaks related to the legacy PC RTC code:
> > 
> >  - Describe the legacy PC RTC driver as such ... it's never quite
> >    been clear that this driver is for PC RTCs, and now it's fair
> >    to call this the "legacy" driver.
> > 
> >  - Force it to understand about HPET stealing its IRQs ... kernel
> >    code does this always when HPET is in use, there should be no
> >    option for users to goof up the config.
> > 
> > This seems to fix kernel bugzilla #10729.
> 
> hm.  "seems" is a bit soft.

Fixes it for one reporter.  Another reporter has yet to respond.


> Do you think this should be in 2.6.26?

Yes, unless someone more involved in the HPET stuff has a better
solution.  (Or that legacy RTC gets a maintainer, who disagrees...)

This does seem to suggest that we have an extra Kconfig variable
here, by the way.

- dave




      reply	other threads:[~2008-06-08 23:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-06  5:41 [patch 2.6.26-rc5] make HPET_RTC_IRQ track HPET_EMULATE_RTC David Brownell
2008-06-06 13:44 ` Maxim Levitsky
2008-06-10 21:31   ` David Brownell
2008-06-11 16:37     ` Maxim Levitsky
2008-06-08 21:00 ` Andrew Morton
2008-06-08 23:05   ` David Brownell [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=200806081605.35042.david-b@pacbell.net \
    --to=david-b@pacbell.net \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox