linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Paul Mackerras <paulus@samba.org>
To: Tom Rini <trini@kernel.crashing.org>
Cc: org@stop.crashing.org, linuxppc-dev@lists.linuxppc.org,
	Dan Malek <dan@embeddededge.com>
Subject: Re: 8xx drivers for 2.6
Date: Mon, 22 Dec 2003 08:39:20 +1100	[thread overview]
Message-ID: <16358.4872.857438.957341@cargo.ozlabs.ibm.com> (raw)
In-Reply-To: <20031211191854.GK23731@stop.crashing.org>


Tom Rini writes:

> (serial), and in 2.6 having request_8xxirq becomes much uglier because
> of the irqreturn_t stuff (at least I couldn't make it happen w/o chaning
> <linux/interrupt.h>, and I never did figure out why cond_syscall()
> doesn't work in some files but not others.

Gaahhhh, I thought we had got rid of request_8xxirq.  I don't want to
see it come back.  And this sort of thing is just bad:

> diff -Nru a/include/asm-ppc/mpc8xx.h b/include/asm-ppc/mpc8xx.h
> --- a/include/asm-ppc/mpc8xx.h	Thu Dec 11 12:14:00 2003
> +++ b/include/asm-ppc/mpc8xx.h	Thu Dec 11 12:14:00 2003
> @@ -96,8 +96,10 @@
>  extern unsigned char __res[];
>
>  struct pt_regs;
> +typedef int irqreturn_t;	/* FIXME -- Tom */
> +

[snip]

> diff -Nru a/include/linux/interrupt.h b/include/linux/interrupt.h
> --- a/include/linux/interrupt.h	Thu Dec 11 12:14:00 2003
> +++ b/include/linux/interrupt.h	Thu Dec 11 12:14:00 2003
> @@ -26,7 +26,9 @@
>   * IRQ_HANDLED means that we did have a valid interrupt and handled it.
>   * IRQ_RETVAL(x) selects on the two depending on x being non-zero (for handled)
>   */
> +#ifndef __CONFIG_8xx_DEFS
>  typedef int irqreturn_t;
> +#endif

Paul.

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  parent reply	other threads:[~2003-12-21 21:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-11 19:18 8xx drivers for 2.6 Tom Rini
2003-12-11 19:44 ` Dan Malek
2003-12-11 21:25   ` Tom Rini
2003-12-15 12:13     ` Pantelis Antoniou
2003-12-15 16:18       ` Tom Rini
2003-12-21 12:31         ` Geert Uytterhoeven
2003-12-21 21:39 ` Paul Mackerras [this message]
2003-12-22  9:00   ` Dan Malek

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=16358.4872.857438.957341@cargo.ozlabs.ibm.com \
    --to=paulus@samba.org \
    --cc=dan@embeddededge.com \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=org@stop.crashing.org \
    --cc=trini@kernel.crashing.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;
as well as URLs for NNTP newsgroup(s).