From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: linux-kernel@vger.kernel.org
Cc: Pieter Palmers <pieterp@joow.be>, Dan Dennedy <dan@dennedy.org>,
linux1394-devel@lists.sourceforge.net
Subject: which header for local_irq_save? (was Re: [PATCH update] ieee1394: cycle timer read extension for raw1394/libraw1394)
Date: Sat, 03 Feb 2007 14:42:15 +0100 [thread overview]
Message-ID: <45C49137.2060103@s5r6.in-berlin.de> (raw)
In-Reply-To: <tkrat.e06f68103e99e517@s5r6.in-berlin.de>
I wrote:
> --- linux.orig/drivers/ieee1394/ieee1394_core.c 2007-01-27 14:07:00.000000000 +0100
> +++ linux/drivers/ieee1394/ieee1394_core.c 2007-02-03 13:47:33.000000000 +0100
> @@ -33,6 +33,9 @@
> #include <linux/skbuff.h>
> #include <linux/suspend.h>
> #include <linux/kthread.h>
> +#include <linux/irqflags.h>
> +#include <linux/preempt.h>
> +#include <linux/time.h>
>
> #include <asm/byteorder.h>
>
Is <linux/irqflags.h> the correct header for local_irq_save/
local_irq_restore? It seems to be <asm/system.h> under Linux 2.6.16 but
I'm not sure about later kernels.
--
Stefan Richter
-=====-=-=== --=- ---==
http://arcgraph.de/sr/
next prev parent reply other threads:[~2007-02-03 14:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <45BA5CFD.6070900@joow.be>
2007-01-27 10:21 ` [RFC] cycle timer read extension for raw1394/libraw1394 Stefan Richter
2007-01-27 10:45 ` Pieter Palmers
2007-01-27 12:48 ` Stefan Richter
2007-02-03 12:58 ` [PATCH update] ieee1394: " Stefan Richter
2007-02-03 13:42 ` Stefan Richter [this message]
2007-02-03 14:22 ` Pieter Palmers
2007-02-03 15:32 ` Stefan Richter
2007-02-04 12:55 ` Pieter Palmers
2007-02-03 16:42 ` Stefan Richter
2007-02-03 19:03 ` Stefan Richter
2007-02-03 20:18 ` Pieter Palmers
2007-02-10 14:20 ` compat_ioctl (was [PATCH update] ieee1394: cycle timer read extension for raw1394/libraw1394) Stefan Richter
2007-02-10 15:47 ` Arnd Bergmann
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=45C49137.2060103@s5r6.in-berlin.de \
--to=stefanr@s5r6.in-berlin.de \
--cc=dan@dennedy.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux1394-devel@lists.sourceforge.net \
--cc=pieterp@joow.be \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.