public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Brownell <david-b@pacbell.net>
To: Clemens Ladisch <clemens@ladisch.de>
Cc: lkml <linux-kernel@vger.kernel.org>,
	bob.picco@hp.com, venkatesh.pallipadi@intel.com,
	Vojtech Pavlik <vojtech@suse.cz>,
	the arch/x86 maintainers <x86@kernel.org>,
	Adrian Bunk <bunk@kernel.org>
Subject: Re: [patch 2.6.26-git] /dev/hpet - fixes and cleanup
Date: Tue, 29 Jul 2008 12:46:25 -0700	[thread overview]
Message-ID: <200807291246.26156.david-b@pacbell.net> (raw)
In-Reply-To: <488D8D16.7010502@ladisch.de>

On Monday 28 July 2008, Clemens Ladisch wrote:
> David Brownell wrote:
> > Oh ... I see.  It's called write_counter() but doesn't
> > actually write the counter.  Likewise, read_counter() is
> > not actually reading the counter.  Gaack ...
> 
> A more correct name would be something like
> write_a_register_that_has_the_same_size_as_a_counter_register().

writel() would be my choice ... :)

I don't think anything in that code really needs to modify the
upper 32 bits of those registers.  And nothing except the ia64
HPET clocksource needs to read them either.

 
> I'm hoping that I can deprecate and delete much of this code without
> having to clean it up first.

I'm not sure how practical that goal is, but I agree that there
seems to be no point to /dev/hpet ... certainly, you could start
by deprecating it and making sure distroes don't enable it.


> > Any comments on the rest?
> 
> Looks fine.  I would have preferred a series of smaller patches, but my
> feelings on this are not strong enough to split it myself or to ask you
> to do it.

OK, I'll send along the updated patch (against 2.6.27-rc1).

- Dave

  reply	other threads:[~2008-07-29 20:06 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-22 22:08 [patch 2.6.26] /dev/hpet - fixes and cleanup David Brownell
2008-07-23  7:44 ` Clemens Ladisch
2008-07-23 16:12   ` David Brownell
2008-07-23 16:50     ` David Brownell
2008-07-24 11:35     ` Clemens Ladisch
2008-07-25 19:55       ` David Brownell
2008-07-29 21:26         ` H. Peter Anvin
2008-07-25 19:58       ` [patch 2.6.26-git] " David Brownell
2008-07-28  7:57         ` Clemens Ladisch
2008-07-28  8:27           ` David Brownell
2008-07-28  9:10             ` Clemens Ladisch
2008-07-29 19:46               ` David Brownell [this message]
2008-07-29 19:47               ` [patch 2.6.27-rc1] " David Brownell
2008-07-31 16:46                 ` Ingo Molnar
2008-07-31 16:55                   ` Ingo Molnar
2008-07-31 19:59                     ` David Brownell
2008-07-31 20:50                       ` Ingo Molnar

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=200807291246.26156.david-b@pacbell.net \
    --to=david-b@pacbell.net \
    --cc=bob.picco@hp.com \
    --cc=bunk@kernel.org \
    --cc=clemens@ladisch.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=venkatesh.pallipadi@intel.com \
    --cc=vojtech@suse.cz \
    --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