From: Ralf Baechle <ralf@linux-mips.org>
To: Yoichi Yuasa <yoichi_yuasa@tripeaks.co.jp>
Cc: linux-mips <linux-mips@linux-mips.org>
Subject: Re: [PATCH][MIPS] fix the installation condition of MIPS clocksource
Date: Wed, 12 Mar 2008 14:02:01 +0000 [thread overview]
Message-ID: <20080312140201.GA25986@linux-mips.org> (raw)
In-Reply-To: <20080218230459.35c2204b.yoichi_yuasa@tripeaks.co.jp>
On Mon, Feb 18, 2008 at 11:04:59PM +0900, Yoichi Yuasa wrote:
> MIPS clocksource has been installed on DEC 5000/200(R3000).
> The installation condition of MIPS clocksource is wrong.
A bug indeed but I figured it was cleaner to have init_mips_clocksource()
itself check for the presence of an r4k style counter like other
device initialitation functions. So I went for a different fix for
both 2.6.24 and master.
Thanks for raising the issue,
Ralf
next prev parent reply other threads:[~2008-03-12 14:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-18 14:04 [PATCH][MIPS] fix the installation condition of MIPS clocksource Yoichi Yuasa
2008-03-12 14:02 ` Ralf Baechle [this message]
2008-03-12 14:50 ` Yoichi Yuasa
2008-03-17 13:05 ` Ralf Baechle
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=20080312140201.GA25986@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=linux-mips@linux-mips.org \
--cc=yoichi_yuasa@tripeaks.co.jp \
/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