From: Thomas Gleixner <tglx@linutronix.de>
To: Jaswinder Singh Rajput <jaswinder@kernel.org>
Cc: Ingo Molnar <mingo@elte.hu>, x86 maintainers <x86@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Andi Kleen <andi@firstfloor.org>
Subject: Re: [git-pull -tip] x86: declaration patches
Date: Fri, 10 Apr 2009 20:11:46 +0200 (CEST) [thread overview]
Message-ID: <alpine.LFD.2.00.0904102010220.21577@localhost.localdomain> (raw)
In-Reply-To: <1239384111.3169.13.camel@ht.satnam>
On Fri, 10 Apr 2009, Jaswinder Singh Rajput wrote:
> On Fri, 2009-04-10 at 18:51 +0200, Thomas Gleixner wrote:
> > On Fri, 10 Apr 2009, Jaswinder Singh Rajput wrote:
> > > #endif /* CONFIG_X86_32 */
> > > diff --git a/arch/x86/kernel/apic/io_apic.c b/arch/x86/kernel/apic/io_apic.c
> > > index 8499000..d1bac67 100644
> > > --- a/arch/x86/kernel/apic/io_apic.c
> > > +++ b/arch/x86/kernel/apic/io_apic.c
> > > @@ -59,6 +59,7 @@
> > > #include <asm/setup.h>
> > > #include <asm/irq_remapping.h>
> > > #include <asm/hpet.h>
> > > +#include <asm/hw_irq.h> /* smp_irq_move_cleanup_interrupt */
> >
> > Can we please avoid these useless comments all over the place ?
> >
>
> I kept these intentionally because few of these declarations I have
> already fixed earlier.
> For example during process.c unification work developers forget to
> include and fix syscalls.h :
And how does such a comment help not to forget anything ? It's useless
information and just irritating to read like all end of line comments.
Thanks,
tglx
next prev parent reply other threads:[~2009-04-10 18:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-10 16:33 Jaswinder Singh Rajput
2009-04-10 16:51 ` Thomas Gleixner
2009-04-10 17:21 ` Jaswinder Singh Rajput
2009-04-10 18:11 ` Thomas Gleixner [this message]
2009-04-10 17:29 ` Sam Ravnborg
2009-04-10 17:45 ` Cyrill Gorcunov
2009-04-10 18:33 ` Jaswinder Singh Rajput
2009-04-12 13:21 ` 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=alpine.LFD.2.00.0904102010220.21577@localhost.localdomain \
--to=tglx@linutronix.de \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=jaswinder@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=x86@kernel.org \
/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
Powered by JetHome