From: Andrew Morton <akpm@linux-foundation.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: lkml@rtr.ca, linux-kernel@vger.kernel.org, Len Brown <lenb@kernel.org>
Subject: Re: [PATCH] Fix /proc/acpi/alarm BCD alarm encodings
Date: Thu, 25 Oct 2007 15:13:34 -0700 [thread overview]
Message-ID: <20071025151334.f8879fe5.akpm@linux-foundation.org> (raw)
In-Reply-To: <alpine.LFD.0.999.0710251502430.30120@woody.linux-foundation.org>
On Thu, 25 Oct 2007 15:04:18 -0700 (PDT)
Linus Torvalds <torvalds@linux-foundation.org> wrote:
>
>
> On Thu, 18 Oct 2007, Andrew Morton wrote:
>
> > On Wed, 17 Oct 2007 23:18:32 -0400
> > Mark Lord <lkml@rtr.ca> wrote:
> >
> > > >and note the "& 0x3f" which is done in BCD mode. Strange. But we always
> > > >write zero (which may or may not be correct). So I'd have to add a mask to
> > > >the interface, and I decided it wasn't worth it until somebody talks about
> > > >how that thing actually works..
> > >
> > > Linus, this is your patch from a few weeks ago.
> > > It (still) solves problems for me here.
> > > This should go into 2.6.24.
> > >
> > > Fix BIN_TO_BCD()/BCD_TO_BIN() handling when setting the real-time alarm clock.
> >
> > This patch is presently (stuck) in -mm. I'll move it to my
> > must-be-in-2.6.24-even-if-the-maintainer-fluffs-it queue.
>
> I noticed that apparently this never happened, and it didn't go into -rc1.
>
> I'll put it there myself, since I'm the author and Mark tested it, and the
> old code was definitely totally buggy. The earlier it gets in, the better,
> in case there are cleanups and/or other issues.
>
I'll send over my copy. I don't think it changed.
prev parent reply other threads:[~2007-10-25 22:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-18 3:18 [PATCH] Fix /proc/acpi/alarm BCD alarm encodings Mark Lord
2007-10-18 22:11 ` Andrew Morton
2007-10-25 22:04 ` Linus Torvalds
2007-10-25 22:13 ` Andrew Morton [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=20071025151334.f8879fe5.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@rtr.ca \
--cc=torvalds@linux-foundation.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