From: "Paul Rolland" <rol@witbe.net>
To: "'Jaroslav Kysela'" <perex@perex.cz>
Cc: <linux-kernel@vger.kernel.org>, <Perex@suze.cz>, <rol@as2917.net>
Subject: Re: [PATCH 2.5.56] Sound core not compiling without /proc support
Date: Sun, 12 Jan 2003 15:15:52 +0100 [thread overview]
Message-ID: <00a201c2ba45$1db90650$2101a8c0@witbe> (raw)
In-Reply-To: <Pine.LNX.4.33.0301121458540.611-100000@pnote.perex-int.cz>
Hello,
> > Here is a quick patch to allow sound support to compile
> correctly when
> > not using /proc support.
>
> It's a bad fix. The null function declarations should go to
> include/sound/info.h.
>
As I wrote, it is a "quick fix".
Sure there are better way to do it, my intention was mainly :
- to mention the problem,
- give a quick (though dirty) workaround for people missing it.
Paul
prev parent reply other threads:[~2003-01-12 14:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-12 12:00 [PATCH 2.5.56] Sound core not compiling without /proc support Paul Rolland
2003-01-12 12:56 ` Sam Ravnborg
2003-01-12 13:59 ` Jaroslav Kysela
2003-01-12 14:15 ` Paul Rolland [this message]
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='00a201c2ba45$1db90650$2101a8c0@witbe' \
--to=rol@witbe.net \
--cc=Perex@suze.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=rol@as2917.net \
/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