From: Bernhard Walle <bwalle@suse.de>
To: Jesper Juhl <jesper.juhl@gmail.com>
Cc: linux-ia64@vger.kernel.org, linux-kernel@vger.kernel.org,
fastboot@lists.osdl.org
Subject: Re: [Fastboot] [PATCH] [REVIEW] Fix irqpoll on IA64 (timer interrupt != 0)
Date: Mon, 19 Mar 2007 18:37:10 +0000 [thread overview]
Message-ID: <20070319183710.GA23499@strauss.suse.de> (raw)
In-Reply-To: <9a8748490703191129h396211e9q59eeea9533d00c38@mail.gmail.com>
* Jesper Juhl <jesper.juhl@gmail.com> [2007-03-19 19:29]:
> >
> > -void
> > +int
> > register_percpu_irq (ia64_vector vec, struct irqaction *action)
> > {
>
> Each and every function example in Documentation/CodingStyle has the
> return type on the same line as the function name, so why not get
> these in-line while you are modifying them anyway?
Because all other functions in that file are coded this way. I think
it looks better if you don't change the style in a particular file.
Am I wrong?
> int register_percpu_irq (ia64_vector vec, struct irqaction *action)
>
>
> > @@ -174,6 +175,13 @@ void note_interrupt(unsigned int irq, st
> > desc->irqs_unhandled = 0;
> > }
> >
> > +
> > +void set_timer_interrupt(unsigned int irq)
>
> Just one blank line between functions, as pr CodingStyle:
> "In source files, separate functions with one blank line. ..."
Fixed (locally). I'll repost if I get feedback of the contents of the
patch.
Regards,
Bernhard
next prev parent reply other threads:[~2007-03-19 18:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-19 18:13 [PATCH] [REVIEW] Fix irqpoll on IA64 (timer interrupt != 0) Bernhard Walle
2007-03-19 18:29 ` Jesper Juhl
2007-03-19 18:37 ` Bernhard Walle [this message]
2007-03-19 18:38 ` [Fastboot] " Jesper Juhl
2007-03-19 20:21 ` Thomas Gleixner
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=20070319183710.GA23499@strauss.suse.de \
--to=bwalle@suse.de \
--cc=fastboot@lists.osdl.org \
--cc=jesper.juhl@gmail.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.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