From: Aurelien Jarno <aurelien@aurel32.net>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] qemu/hw slavio_intctl.c slavio_timer.c sun4m.c
Date: Tue, 1 Jan 2008 22:26:28 +0100 [thread overview]
Message-ID: <20080101212628.GA22333@hall.aurel32.net> (raw)
In-Reply-To: <f43fc5580801011300m626adf0bpcb758d799644d29f@mail.gmail.com>
On Tue, Jan 01, 2008 at 11:00:46PM +0200, Blue Swirl wrote:
> On 1/1/08, Aurelien Jarno <aurelien@aurel32.net> wrote:
> > On Sat, Dec 29, 2007 at 08:09:57PM +0000, Blue Swirl wrote:
> > > CVSROOT: /cvsroot/qemu
> > > Module name: qemu
> > > Changes by: Blue Swirl <blueswir1> 07/12/29 20:09:57
> > >
> > > Modified files:
> > > hw : slavio_intctl.c slavio_timer.c sun4m.c
> > >
> > > Log message:
> > > Fix CPU timer interrupts
> > >
> > > CVSWeb URLs:
> > > http://cvs.savannah.gnu.org/viewcvs/qemu/hw/slavio_intctl.c?cvsroot=qemu&r1=1.26&r2=1.27
> > > http://cvs.savannah.gnu.org/viewcvs/qemu/hw/slavio_timer.c?cvsroot=qemu&r1=1.26&r2=1.27
> > > http://cvs.savannah.gnu.org/viewcvs/qemu/hw/sun4m.c?cvsroot=qemu&r1=1.76&r2=1.77
> > >
> >
> > Unfortunately this commit has broken SS-5 running Linux:
>
> The fix is now in CVS, please give it a test.
>
I confirm that it works. Thanks a lot for the quick fix.
--
.''`. Aurelien Jarno | GPG: 1024D/F1BCDB73
: :' : Debian developer | Electrical Engineer
`. `' aurel32@debian.org | aurelien@aurel32.net
`- people.debian.org/~aurel32 | www.aurel32.net
prev parent reply other threads:[~2008-01-01 21:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-29 20:09 [Qemu-devel] qemu/hw slavio_intctl.c slavio_timer.c sun4m.c Blue Swirl
2008-01-01 19:25 ` Aurelien Jarno
2008-01-01 20:00 ` Blue Swirl
2008-01-01 20:25 ` Andreas Färber
2008-01-01 21:00 ` Blue Swirl
2008-01-01 21:26 ` Aurelien Jarno [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=20080101212628.GA22333@hall.aurel32.net \
--to=aurelien@aurel32.net \
--cc=blauwirbel@gmail.com \
--cc=qemu-devel@nongnu.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).