LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: "Miguel Botón" <mboton.lkml@gmail.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Kevin Winchester <kjwinchester@gmail.com>,
"H. Peter Anvin" <hpa@zytor.com>,
Thomas Gleixner <tglx@linutronix.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: hwclock failure in x86.git
Date: Sat, 12 Jan 2008 00:58:04 +0100 [thread overview]
Message-ID: <200801120058.05398.mboton@gmail.com> (raw)
In-Reply-To: <20080111140346.GA13604@elte.hu>
On Friday 11 January 2008 15:03:47 Ingo Molnar wrote:
> * Kevin Winchester <kjwinchester@gmail.com> wrote:
> > Bisect says...
> >
> > 4b5ea240a0c05ff90c4959fd91f0caec7b9bef1b is first bad commit
> > commit 4b5ea240a0c05ff90c4959fd91f0caec7b9bef1b
> > Author: mboton@gmail.com <mboton@gmail.com>
> > Date: Wed Jan 9 13:31:11 2008 +0100
> >
> > x86: ioport_{32|64}.c unification
>
> thanks for tracking it down. I pulled that commit for now. But it would
> be nice to figure out what's going on there.
>
> Ingo
mmm, i'll try to reproduce it tomorrow and find a fix.
thanks for notifying this problem.
--
Miguel Botón
next prev parent reply other threads:[~2008-01-11 23:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-10 23:28 Kevin Winchester
2008-01-10 23:32 ` H. Peter Anvin
2008-01-10 23:50 ` Kevin Winchester
2008-01-11 1:13 ` H. Peter Anvin
2008-01-11 2:04 ` Kevin Winchester
2008-01-11 14:03 ` Ingo Molnar
2008-01-11 23:58 ` Miguel Botón [this message]
2008-01-12 1:04 ` [PATCH] x86: fix ioport unification on 32-bit [was: Re: hwclock failure in x86.git] Chris Wright
2008-01-12 1:06 ` [PATCH] x86: refactor ioport unification Chris Wright
2008-01-14 8:32 ` Ingo Molnar
2008-01-14 8:27 ` [PATCH] x86: fix ioport unification on 32-bit [was: Re: hwclock failure in x86.git] Ingo Molnar
2008-01-11 2:27 ` hwclock failure in x86.git Kevin Winchester
2008-01-11 2:55 ` Zach Brown
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=200801120058.05398.mboton@gmail.com \
--to=mboton.lkml@gmail.com \
--cc=hpa@zytor.com \
--cc=kjwinchester@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--subject='Re: hwclock failure in x86.git' \
/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
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).