mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjanv@redhat.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: Achim_Leubner@adaptec.com
Subject: Re: [PATCH] gdth update
Date: Wed, 29 Sep 2004 13:42:39 +0200	[thread overview]
Message-ID: <1096458159.2786.28.camel@laptop.fenrus.com> (raw)
In-Reply-To: <200409281401.i8SE1dXL006887@hera.kernel.org>

[-- Attachment #1: Type: text/plain, Size: 1208 bytes --]

On Tue, 2004-09-28 at 13:12, Linux Kernel Mailing List wrote:
>   * IO-mapping with virt_to_bus(), gdth_readb(), gdth_writeb(), ...
> - * register_reboot_notifier() to get a notify on shutdown used
> + * register_reboot_notifier() to get a notify on shutown used

why this change ?

> +#if LINUX_VERSION_CODE >= KERNEL_VERSION(2,6,0)
> +static irqreturn_t gdth_interrupt(int irq, void *dev_id, struct pt_regs *regs);
>  #else
> -static void gdth_interrupt(int irq,struct pt_regs *regs);
> +static void gdth_interrupt(int irq, void *dev_id, struct pt_regs *regs);
>  #endif

this really is the wrong way to do such irq prototype compatibility in
drivers. *really*


> +static struct file_operations gdth_fops = {
> +#if LINUX_VERSION_CODE >= KERNEL_VERSION(2,6,0)
> +    .ioctl   = gdth_ioctl,
> +    .open    = gdth_open,
> +    .release = gdth_close,
> +#else
> +    ioctl:gdth_ioctl,
> +    open:gdth_open,
> +    release:gdth_close,
> +#endif

C99 initializers work in all kernel versions since it's a property of
the C compiler not of the kernel. I wonder why you are putting this
ifdef here....

the rest of your ifdefs are generally quite fishy too unfortionately... 

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

       reply	other threads:[~2004-09-29 11:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200409281401.i8SE1dXL006887@hera.kernel.org>
2004-09-29 11:42 ` Arjan van de Ven [this message]
2004-09-29 12:15 Leubner, Achim
2004-09-29 12:41 ` Christoph Hellwig
2004-09-29 13:43 ` Jörn Engel
2004-09-29 14:21   ` Christoph Hellwig
2004-09-29 14:28 Leubner, Achim

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=1096458159.2786.28.camel@laptop.fenrus.com \
    --to=arjanv@redhat.com \
    --cc=Achim_Leubner@adaptec.com \
    --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

all inboxes | Powered by JetHome®