From: Cyrill Gorcunov <gorcunov@gmail.com>
To: mingo@elte.hu, hpa@zytor.com, tglx@linutronix.de,
macro@linux-mips.org, yhlu.kernel@gmail.com
Cc: linux-kernel@vger.kernel.org
Subject: [patch 0/2] -tip x86/apic helper for further merging
Date: Tue, 15 Jul 2008 21:02:53 +0400 [thread overview]
Message-ID: <487cd9a9.08074e0a.1dd7.20cd@mx.google.com> (raw)
Hi, these two patches add calibrate_APIC_clock in 32bit code as
we have in 64bit code and make it to return error. I don't see
the way to make it simplier by now since 32bit code uses a few
clock sources.
Also this contains already passed patch
[RFC] lapic calibration results fix
http://lkml.org/lkml/2008/7/13/50
Please review, any comments are welcome.
The patches are made on top of -tip tree
commit d093f36037d9f296c7886d11d3fd67ee4ca817b3
Merge: ff8db60... a6784ad...
Author: Ingo Molnar <mingo@elte.hu>
Date: Thu Jul 10 12:36:55 2008 +0200
Merge branch 'x86/core'
- Cyrill -
--
next reply other threads:[~2008-07-15 17:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-15 17:02 Cyrill Gorcunov [this message]
2008-07-18 12:17 ` [patch 0/2] -tip x86/apic helper for further merging Ingo Molnar
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=487cd9a9.08074e0a.1dd7.20cd@mx.google.com \
--to=gorcunov@gmail.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=macro@linux-mips.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=yhlu.kernel@gmail.com \
/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