Just some code beautification. Nothing else.
Signed-off-by: Cyrill Gorcunov <gorcunov@gmail.com>

---
Index: linux-2.6.git/arch/x86/kernel/cpu/perfctr-watchdog.c

====================================================================

--- linux-2.6.git.orig/arch/x86/kernel/cpu/perfctr-watchdog.c	2008-06-21 13:21:54.000000000 +0400

+++ linux-2.6.git/arch/x86/kernel/cpu/perfctr-watchdog.c	2008-06-21 19:08:17.000000000 +0400

@@ -1,11 +1,15 @@

-/* local apic based NMI watchdog for various CPUs.

-   This file also handles reservation of performance counters for coordination

-   with other users (like oprofile).

-

-   Note that these events normally don't tick when the CPU idles. This means

-   the frequency varies with CPU load.

-

-   Original code for K7/P6 written by Keith Owens */

+/*

+ * local apic based NMI watchdog for various CPUs.

+ *

+ * This file also handles reservation of performance counters for coordination

+ * with other users (like oprofile).

+ *

+ * Note that these events normally don't tick when the CPU idles. This means

+ * the frequency varies with CPU load.

+ *

+ * Original code for K7/P6 written by Keith Owens

+ *

+ */
 #include <linux/percpu.h>

 #include <linux/module.h>

@@ -36,12 +40,16 @@ struct wd_ops {
 static const struct wd_ops *wd_ops;
-/* this number is calculated from Intel's MSR_P4_CRU_ESCR5 register and it's

- * offset from MSR_P4_BSU_ESCR0.  It will be the max for all platforms (for now)

+/*

+ * this number is calculated from Intel's MSR_P4_CRU_ESCR5 register and it's

+ * offset from MSR_P4_BSU_ESCR0.

+ *

+ * It will be the max for all platforms (for now)

  */

 #define NMI_MAX_COUNTER_BITS 66
-/* perfctr_nmi_owner tracks the ownership of the perfctr registers:

+/*

+ * perfctr_nmi_owner tracks the ownership of the perfctr registers:

  * evtsel_nmi_owner tracks the ownership of the event selection

  * - different performance counters/ event selection may be reserved for

  *   different subsystems this reservatio...
[ message continues ]

On Monday 01 January 2007 10:45, you wrote:

|  Cyrill V. Gorcnov wrote:

|  > On Monday 01 January 2007 04:19, you wrote:

|  > |

|  > |  In order to not get in trouble with MADR ("Mothers Against Drunk

|  > |  Releases") I decided to cut the 2.6.20-rc3 release early rather than wait

|  > |  for midnight, because it's bound to be new years _somewhere_ out there. So

|  > |  here's to a happy 2007 for everybody.

|  > |

|  >

|  > I've tried to clone linux git repo and got:

|  >

|  > 	git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git

|  > 	fatal: unexpected EOF

|  > 	fetch-pack from 'git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git' failed.

|  >

|  > What's wrong?

|

|  I think that git does not like year rollover.  I've tried it after Linus

|  sent message out, and it was not giving me anything new (cca from 5PM

|  PST when Linus sent change to 8PM).  Then it gave out random changes

|  (8PM to 9PM).  After that it was dead, as you've noticed.  But after

|  that I was able to get 2.6.20-rc3 out - compiling now.   So perhaps just

|  try it again...

|  								Petr

|

|  P.S.: Happy New Year.  Here in California we still have 15 minutes of

|  year 2006 to go.

|

|

|  
Yea, I've got linux git clone later. I think that was some files activity

on git server so that is why I was noticed with "fatal: unexpected EOF" git

message.
--

	- Cyrill

-

applied, thanks Cyrill.
note, your mailer sets the wrong timestamps:
| Date: Thu, 01 Jan 1970 03:00:01 +0300

| From: Cyrill Gorcunov <gorcunov@gmail.com>
i'll edit them out of your patches so that Git doesnt get bogus dates.
	Ingo

--

[Ingo Molnar - Tue, Jun 24, 2008 at 06:36:22PM +0200]

|

| * Cyrill Gorcunov <gorcunov@gmail.com> wrote:

|

| > Just some code beautification. Nothing else.

|

| applied, thanks Cyrill.

|

| note, your mailer sets the wrong timestamps:

|

| | Date: Thu, 01 Jan 1970 03:00:01 +0300

| | From: Cyrill Gorcunov <gorcunov@gmail.com>

|

| i'll edit them out of your patches so that Git doesnt get bogus dates.

|

| 	Ingo

| 
Thanks Ingo, I've mentoined in 'reply' mail for first message

in series that somehow happened that date was screwed up.

I can resent the series if needed.
		- Cyrill -

--

no need to resend, fixed it all up :-)
	Ingo

--

Thanks a lot, Ingo
--