Re: generic clockevents/ (hr)time(r) patches was Re: -mm mergeplans for 2.6.23

[Andrew Morton]

On Thu, 12 Jul 2007 01:03:28 +0200
Thomas Gleixner <tglx@xxxxxxxxxxxxx> wrote:

> Andrew, Linus, 
> 
> On Tue, 2007-07-10 at 01:31 -0700, Andrew Morton wrote:
> > When replying, please rewrite the subject suitably and try to Cc: the
> > appropriate developer(s).
> 
> > i386-hpet-check-if-the-counter-works.patch
> > nohz-fix-nohz-x86-dyntick-idle-handling.patch
> > acpi-move-timer-broadcast-and-pmtimer-access-before-c3-arbiter-shutdown.patch
> > clockevents-fix-typo-in-acpi_pmc.patch
> > timekeeping-fixup-shadow-variable-argument.patch
> > timerc-cleanup-recently-introduced-whitespace-damage.patch
> > clockevents-remove-prototypes-of-removed-functions.patch
> > clockevents-fix-resume-logic.patch
> > clockevents-fix-device-replacement.patch
> > tick-management-spread-timer-interrupt.patch
> > highres-improve-debug-output.patch
> > hrtimer-speedup-hrtimer_enqueue.patch
> > pcspkr-use-the-global-pit-lock.patch
> > ntp-move-the-cmos-update-code-into-ntpc.patch
> > i386-pit-stop-only-when-in-periodic-or-oneshot-mode.patch
> > i386-remove-volatile-in-apicc.patch
> > i386-hpet-assumes-boot-cpu-is-0.patch
> > i386-move-pit-function-declarations-and-constants-to-correct-header-file.patch
> 
> These got sent to Andi as well, but the patches are independent of the
> x86_64 conversion.
> 
> These are bugfixes (nohz-fix-nohz-x86-dyntick-idle-handling.patch) and
> general improvements of the core code and the existing i386 code.
> 
> Can we please merge the above now ?
> 
> I can resend them or setup a git repo if you want.
> 
> Andi, any objections against the above i386 fixlets ?
> 

They all look pretty innocuous to me.

Could you please take a second look, decide if any of them should also be
in 2.6.22.x and let me know?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/