Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Grant Grundler <grundler@parisc-linux.org>
To: Kars de Jong <jongk@linux-m68k.org>
Cc: Helge Deller <deller@gmx.de>,
	Linux/m68k kernel mailing list <linux-m68k@lists.linux-m68k.org>,
	Geert Uytterhoeven <geert@linux-m68k.org>,
	parisc-linux@parisc-linux.org
Subject: Re: [parisc-linux] Re: [PATCH] missing exports
Date: Sat, 10 Jul 2004 14:33:18 -0600	[thread overview]
Message-ID: <20040710203318.GC27696@colo.lackof.org> (raw)
In-Reply-To: <1089477389.2474.129.camel@kars.perseus.home>

On Sat, Jul 10, 2004 at 06:36:30PM +0200, Kars de Jong wrote:
...
> @@ -284,6 +286,9 @@
>  #ifdef __hppa__
>  	struct parisc_device	*dev;
>  	int		dev_err;	/* carries status from registration */
> +#elif defined(__mc68000__)
> +	void		*dev;

Can *dev be unified eventually to "struct device"?

"void *" isn't my favorite construct.

grant

  parent reply	other threads:[~2004-07-10 20:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200310192126.23242@smurf.noris.de>
     [not found] ` <3F956F6D.9080803@linux-m68k.org>
     [not found]   ` <1066936308.3338.16.camel@kars.perseus.home>
     [not found]     ` <1066944872.3338.30.camel@kars.perseus.home>
     [not found]       ` <Pine.LNX.4.44.0310240032470.17548-100000@serv>
     [not found]         ` <1067083687.3876.17.camel@kars.perseus.home>
     [not found]           ` <Pine.LNX.4.44.0310251514190.17548-100000@serv>
     [not found]             ` <1067091946.3876.42.camel@kars.perseus.home>
     [not found]               ` <Pine.LNX.4.44.0310252030410.17548-100000@serv>
     [not found]                 ` <1067288209.3591.1.camel@kars.perseus.home>
     [not found]                   ` <1085155984.5069.10.camel@kars.perseus.home>
     [not found]                     ` <Pine.LNX.4.58.0405230227360.10291@scrub.local>
     [not found]                       ` <1085347402.3690.1.camel@kars.perseus.home>
     [not found]                         ` <Pine.GSO.4.58.0405241034430.17985@waterleaf.sonytel.be>
     [not found]                           ` <1085517198.6880.26.camel@kars.perseus.home>
     [not found]                             ` <Pine.GSO.4.58.0405261015580.28417@waterleaf.sonytel.be>
     [not found]                               ` <1085597752.2373.6.camel@kars.perseus.home>
     [not found]                                 ` <1089405759.2674.14.camel@kars.perseus.home>
2004-07-10  9:09                                   ` [parisc-linux] Re: [PATCH] missing exports Geert Uytterhoeven
2004-07-10 13:05                                     ` Matthew Wilcox
2004-07-10 13:55                                       ` Helge Deller
2004-07-10 16:36                                         ` Kars de Jong
2004-07-10 18:08                                           ` Geert Uytterhoeven
2004-07-10 20:33                                           ` Grant Grundler [this message]
2004-07-11 22:16                                           ` Helge Deller
2004-07-12  1:55                                             ` Matthew Wilcox

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=20040710203318.GC27696@colo.lackof.org \
    --to=grundler@parisc-linux.org \
    --cc=deller@gmx.de \
    --cc=geert@linux-m68k.org \
    --cc=jongk@linux-m68k.org \
    --cc=linux-m68k@lists.linux-m68k.org \
    --cc=parisc-linux@parisc-linux.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