linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Gustavo F. Padovan" <gustavo@las.ic.unicamp.br>
To: linux-kernel@vger.kernel.org
Cc: mingo@elte.hu
Subject: [PATCH 08/24] x86: kernel/io_apic_64.c cleanup
Date: Mon, 28 Jul 2008 18:09:15 -0300	[thread overview]
Message-ID: <1217279371-4410-9-git-send-email-gustavo@las.ic.unicamp.br> (raw)
In-Reply-To: <1217279371-4410-8-git-send-email-gustavo@las.ic.unicamp.br>

Remove additional whitespaces.

Signed-off-by: Gustavo F. Padovan <gustavo@las.ic.unicamp.br>
---
 arch/x86/kernel/io_apic_64.c |   18 +++++++++---------
 1 files changed, 9 insertions(+), 9 deletions(-)

diff --git a/arch/x86/kernel/io_apic_64.c b/arch/x86/kernel/io_apic_64.c
index 8269434..f2f1825 100644
--- a/arch/x86/kernel/io_apic_64.c
+++ b/arch/x86/kernel/io_apic_64.c
@@ -1510,14 +1510,14 @@ static void ack_apic_level(unsigned int irq)
 }
 
 static struct irq_chip ioapic_chip __read_mostly = {
-	.name 		= "IO-APIC",
-	.startup 	= startup_ioapic_irq,
-	.mask	 	= mask_IO_APIC_irq,
-	.unmask	 	= unmask_IO_APIC_irq,
-	.ack 		= ack_apic_edge,
-	.eoi 		= ack_apic_level,
+	.name		= "IO-APIC",
+	.startup	= startup_ioapic_irq,
+	.mask		= mask_IO_APIC_irq,
+	.unmask		= unmask_IO_APIC_irq,
+	.ack		= ack_apic_edge,
+	.eoi		= ack_apic_level,
 #ifdef CONFIG_SMP
-	.set_affinity 	= set_ioapic_affinity_irq,
+	.set_affinity	= set_ioapic_affinity_irq,
 #endif
 	.retrigger	= ioapic_retrigger_irq,
 };
@@ -1591,14 +1591,14 @@ static void lapic_register_intr(int irq)
 static void __init setup_nmi(void)
 {
 	/*
- 	 * Dirty trick to enable the NMI watchdog ...
+	 * Dirty trick to enable the NMI watchdog ...
 	 * We put the 8259A master into AEOI mode and
 	 * unmask on all local APICs LVT0 as NMI.
 	 *
 	 * The idea to use the 8259A in AEOI mode ('8259A Virtual Wire')
 	 * is from Maciej W. Rozycki - so we do not have to EOI from
 	 * the NMI handler or the timer interrupt.
-	 */ 
+	 */
 	printk(KERN_INFO "activating NMI Watchdog ...");
 
 	enable_NMI_through_LVT0();
-- 
1.5.4.5


  reply	other threads:[~2008-07-28 21:12 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-28 21:09 [PATCH 0/24] x86: arch/x86/kernel/ cleanups Gustavo F. Padovan
2008-07-28 21:09 ` [PATCH 01/24] x86: kernel/alternative.c cleanup Gustavo F. Padovan
2008-07-28 21:09   ` [PATCH 02/24] x86: kernel/apm_32.c cleanup Gustavo F. Padovan
2008-07-28 21:09     ` [PATCH 03/24] x86: kernel/asm-offsets_64.c cleanup Gustavo F. Padovan
2008-07-28 21:09       ` [PATCH 04/24] x86: kernel/efi.c cleanup Gustavo F. Padovan
2008-07-28 21:09         ` [PATCH 05/24] x86: kernel/cpuid.c cleanup Gustavo F. Padovan
2008-07-28 21:09           ` [PATCH 06/24] x86: kernel/early-quirks.c cleanup Gustavo F. Padovan
2008-07-28 21:09             ` [PATCH 07/24] x86: kernel/io_apic_32.c cleanup Gustavo F. Padovan
2008-07-28 21:09               ` Gustavo F. Padovan [this message]
2008-07-28 21:09                 ` [PATCH 09/24] x86: kernel/irq_64.c cleanup Gustavo F. Padovan
2008-07-28 21:09                   ` [PATCH 10/24] x86: kernel/irqinit_32.c cleanup Gustavo F. Padovan
2008-07-28 21:09                     ` [PATCH 11/24] x86: kernel/kprobes.c cleanup Gustavo F. Padovan
2008-07-28 21:09                       ` [PATCH 12/24] x86: kernel/microcode.c cleanup Gustavo F. Padovan
2008-07-28 21:09                         ` [PATCH 13/24] x86: kernel/module_64.c cleanup Gustavo F. Padovan
2008-07-28 21:09                           ` [PATCH 14/24] x86: kernel/pci-calgary_64.c cleanup Gustavo F. Padovan
2008-07-28 21:09                             ` [PATCH 15/24] x86: kernel/probe_roms_32.c cleanup Gustavo F. Padovan
2008-07-28 21:09                               ` [PATCH 16/24] x86: kernel/process_32.c cleanup Gustavo F. Padovan
2008-07-28 21:09                                 ` [PATCH 17/24] x86: kernel/process_64.c cleanup Gustavo F. Padovan
2008-07-28 21:09                                   ` [PATCH 18/24] x86: kernel/signal_64.c cleanup Gustavo F. Padovan
2008-07-28 21:09                                     ` [PATCH 19/24] x86: kernel/traps_64.c cleanup Gustavo F. Padovan
2008-07-28 21:09                                       ` [PATCH 20/24] x86: kernel/tsc.c cleanup Gustavo F. Padovan
2008-07-28 21:09                                         ` [PATCH 21/24] x86: kernel/visws_quirks.c cleanup Gustavo F. Padovan
2008-07-28 21:09                                           ` [PATCH 22/24] x86: kernel/vmi_32.c cleanup Gustavo F. Padovan
2008-07-28 21:09                                             ` [PATCH 23/24] x86: kernel/vmiclock_32.c cleanup Gustavo F. Padovan
2008-07-28 21:09                                               ` [PATCH 24/24] x86: kernel/sys_x86_64.c cleanup Gustavo F. Padovan
2008-07-29  1:47                       ` [PATCH 11/24] x86: kernel/kprobes.c cleanup Masami Hiramatsu
2008-08-07  9:47     ` [PATCH 02/24] x86: kernel/apm_32.c cleanup Robert Richter
2008-07-28 21:17 ` [PATCH 0/24] x86: arch/x86/kernel/ cleanups Jeremy Fitzhardinge
2008-07-28 21:20 ` Ingo Molnar
2008-07-28 21:37   ` Gustavo F. Padovan

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=1217279371-4410-9-git-send-email-gustavo@las.ic.unicamp.br \
    --to=gustavo@las.ic.unicamp.br \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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).