mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Thomas DuBuisson <thomas.dubuisson@gmail.com>
Cc: linux-kernel@vger.kernel.org, Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH] Include hrtimer.h for ANSI compliance
Date: Tue, 13 Oct 2009 16:34:14 -0700	[thread overview]
Message-ID: <20091013163414.62ec9244.akpm@linux-foundation.org> (raw)
In-Reply-To: <4c44d90b0910061520o36adc7m50419be3a3d9d0fa@mail.gmail.com>

On Tue, 6 Oct 2009 15:20:16 -0700
Thomas DuBuisson <thomas.dubuisson@gmail.com> wrote:

> Include <linux/hrtimer.h> to make pci.h ansi compliant (it references
> an hrtimer enum).

extern enum hrtimer_restart it_real_fn(struct hrtimer *);


Perhaps the declaration of it_real_fn() should be moved to hrtimer.h
instead.  Or perhaps not.


Or we could "forward declare" the enum with simply

enum hrtimer_restart;

but given that the compiler works out the storage size of the type at
compile-time, that looks risky.


Or we could not do anything.  Because increasing our inclusion
complexity for no known gain isn't a bargain.


Or is it no known gain?  What prompted you to write this patch?  Some
error message or warning from some tool?  If so, please describe it
fully.

> 
> diff --git a/include/linux/timer.h b/include/linux/timer.h
> index a2d1eb6..ad2b3cb 100644
> --- a/include/linux/timer.h
> +++ b/include/linux/timer.h
> @@ -6,6 +6,7 @@
> #include <linux/stddef.h>
> #include <linux/debugobjects.h>
> #include <linux/stringify.h>
> +#include <linux/hrtimer.h>
> 
> struct tvec_base;

Your email client mangles whitespace, thus destroying the patch.

      reply	other threads:[~2009-10-13 23:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-06 22:20 Thomas DuBuisson
2009-10-13 23:34 ` Andrew Morton [this message]

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=20091013163414.62ec9244.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --cc=thomas.dubuisson@gmail.com \
    /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