From: Christer Weinigel <wingel@nano-system.com>
To: Arnaldo Carvalho de Melo <acme@conectiva.com.br>
Cc: Adrian Bunk <bunk@fs.tum.de>,
linux-kernel@vger.kernel.org, alan@lxorguk.ukuu.org.uk
Subject: Re: scx200_gpio.c doesn't compile in 2.5.50
Date: 01 Dec 2002 00:35:29 +0100 [thread overview]
Message-ID: <87isyehbr2.fsf@zoo.weinigel.se> (raw)
In-Reply-To: <20021130231622.GO30931@conectiva.com.br>
Arnaldo Carvalho de Melo <acme@conectiva.com.br> writes:
> Em Sat, Nov 30, 2002 at 11:49:39PM +0100, Christer Weinigel escreveu:
> > Adrian Bunk <bunk@fs.tum.de> writes:
> >
> > > Compilation of drivers/char/scx200_gpio.c fails in 2.5.50 with the error
> > > messages below.
> >
> > Thanks for the report. Patch follows.
> >
> > Alan, do you want small fixes like these or should I send them to
> > someone else?
>
> I have this one on my misc-2.5 bk tree that I'll be pushing to Linus
> RSN. It is also required that we include kdev_t.h, as this driver uses the
> minor() macro.
Thanks. Is there any list of what include files one must use to use
for example the minor macro? I looked at fs.h and saw that it
included kdev_t.h so I skipped including that file myself. But
relying on things like that is what bit me to begin with.
/Christer
--
"Just how much can I get away with and still go to heaven?"
Freelance consultant specializing in device driver programming for Linux
Christer Weinigel <christer@weinigel.se> http://www.weinigel.se
next prev parent reply other threads:[~2002-11-30 23:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-28 1:35 scx200_gpio.c doesn't compile in 2.5.50 Adrian Bunk
2002-11-30 22:49 ` Christer Weinigel
2002-11-30 23:16 ` Arnaldo Carvalho de Melo
2002-11-30 23:35 ` Christer Weinigel [this message]
2002-11-30 23:43 ` Arnaldo Carvalho de Melo
2002-12-01 2:45 ` Alan Cox
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=87isyehbr2.fsf@zoo.weinigel.se \
--to=wingel@nano-system.com \
--cc=acme@conectiva.com.br \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bunk@fs.tum.de \
--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