linux-acpi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Andrew Morton <akpm@osdl.org>,
	linux-pm@osdl.org, Martin Lorenz <martin@lorenz.eu.org>,
	linux-acpi@vger.kernel.org, Ernst Herzberg <earny@net4u.de>,
	Hugh Dickins <hugh@veritas.com>, Adrian Bunk <bunk@stusta.de>,
	Andi Kleen <ak@suse.de>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.19-rc <-> ThinkPads
Date: Wed, 01 Nov 2006 17:35:55 -0500	[thread overview]
Message-ID: <4549214B.1000103@tmr.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0610312206390.25218@g5.osdl.org>

Linus Torvalds wrote:

> I wonder if the order matters more, though. Andi? We _used_ to write the 
> high word first, and I think the order matters. The low word contains the 
> enable bit, for example, so when enabling an interrupt, you should write 
> the low word last, when you disable it you should write the low word 
> first.
> 
Although you can argue that anyone coding here should be a guru, in 
practice things this subtle really would be helped by a comment in the 
initial code. I don't agree that "if it was hard to write it should be 
hard to understand." Clearly several competent people missed this 
dependency, or the patch would not have gone in.

-- 
Bill Davidsen <davidsen@tmr.com>
   Obscure bug of 2004: BASH BUFFER OVERFLOW - if bash is being run by a
normal user and is setuid root, with the "vi" line edit mode selected,
and the character set is "big5," an off-by-one errors occurs during
wildcard (glob) expansion.

  parent reply	other threads:[~2006-11-01 22:35 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.64.0610231618510.3962@g5.osdl.org>
2006-10-24 20:21 ` 2.6.19-rc3: known unfixed regressions Adrian Bunk
2006-10-26 22:45 ` 2.6.19-rc3: known unfixed regressions (v2) Adrian Bunk
2006-10-29 23:13 ` 2.6.19-rc3: known unfixed regressions (v3) Adrian Bunk
2006-10-30 13:56   ` Michael S. Tsirkin
2006-10-30 15:27     ` Martin Lorenz
2006-10-30 16:17     ` Jun'ichi Nomura
2006-10-30 16:32       ` Michael S. Tsirkin
2006-10-30 17:20         ` Jun'ichi Nomura
2006-10-30 17:54           ` Michael S. Tsirkin
2006-10-30 16:44       ` Linus Torvalds
2006-10-30 17:34         ` Jun'ichi Nomura
2006-10-30 18:16           ` Linus Torvalds
2006-10-30 18:35             ` Adrian Bunk
2006-10-30 19:00               ` Michael S. Tsirkin
2006-10-30 19:06               ` Hugh Dickins
2006-10-31 12:47               ` Martin Lorenz
2006-10-30 18:58             ` Michael S. Tsirkin
2006-10-31 21:15             ` Michael S. Tsirkin
2006-11-01  3:01     ` 2.6.19-rc <-> ThinkPads Adrian Bunk
2006-11-01  3:15       ` Len Brown
2006-11-01  5:11         ` Ernst Herzberg
2006-11-01  5:26           ` Linus Torvalds
2006-11-01  5:54             ` Michael S. Tsirkin
2006-11-01  6:16               ` Linus Torvalds
2006-11-01 17:25                 ` Andi Kleen
2006-11-01 18:12                   ` Michael S. Tsirkin
2006-11-01 18:25                   ` Linus Torvalds
2006-11-01 19:33                     ` Michael S. Tsirkin
2006-11-01 19:44                       ` Linus Torvalds
2006-11-01 19:34                     ` Andi Kleen
2006-11-01 19:52                       ` Linus Torvalds
2006-11-01 21:15                         ` Andi Kleen
2006-11-01 22:35                 ` Bill Davidsen [this message]
2006-11-01  6:18               ` Michael S. Tsirkin
2006-11-01  9:33                 ` Pavel Machek
2006-11-01 12:02                   ` Michael S. Tsirkin
2006-11-01 17:17                 ` Andi Kleen
2006-11-01 13:50             ` Stefan Seyfried
2006-11-01 16:36       ` Hugh Dickins
2006-11-04  3:49       ` 2.6.19-rc <-> ThinkPads, summary Adrian Bunk
2006-11-04 13:51         ` Hugh Dickins
2006-11-04 14:04         ` Russell King
2006-11-05  6:23           ` Adrian Bunk
2006-11-17  1:53         ` 2.6.19-rc <-> ThinkPads, (related Ubuntu bug report) Mark Stosberg

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=4549214B.1000103@tmr.com \
    --to=davidsen@tmr.com \
    --cc=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=bunk@stusta.de \
    --cc=earny@net4u.de \
    --cc=hugh@veritas.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@osdl.org \
    --cc=martin@lorenz.eu.org \
    --cc=torvalds@osdl.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;
as well as URLs for NNTP newsgroup(s).