From: Frank Davis <fdavis@si.rr.com>
To: Thomas Molina <tmolina@cox.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: compile error and fix in v_midi.c
Date: Sun, 22 Sep 2002 11:51:33 -0400 [thread overview]
Message-ID: <3D8DE705.9090907@si.rr.com> (raw)
In-Reply-To: Pine.LNX.4.44.0209221033440.959-100000@dad.molina
Thomas,
This patch was submited before:
http://marc.theaimsgroup.com/?l=linux-kernel&m=103156669011988&w=2
and also by myself back in 2.5.33
http://marc.theaimsgroup.com/?l=linux-kernel&m=103094246825436&w=2
but hasn't been included yet.
Regards,
Frank
Thomas Molina wrote:
> Compiling 2.5.3[78] I get the following:
>
> v_midi.c: In function `v_midi_open':
> v_midi.c:55: structure has no member named `lock'
> v_midi.c:58: structure has no member named `lock'
> v_midi.c:62: structure has no member named `lock'
> v_midi.c: In function `v_midi_close':
> v_midi.c:83: structure has no member named `lock'
> v_midi.c:87: structure has no member named `lock'
> v_midi.c: In function `attach_v_midi':
> v_midi.c:223: structure has no member named `lock'
> v_midi.c:244: structure has no member named `lock'
> make[2]: *** [v_midi.o] Error 1
> make[1]: *** [oss] Error 2
> make: *** [sound] Error 2
>
> The following patch fixes that:
>
> --- linux-2.5-tm/sound/oss/v_midi.h.old Sun Sep 22 10:01:43 2002
> +++ linux-2.5-tm/sound/oss/v_midi.h Sun Sep 22 10:02:48 2002
> @@ -11,5 +11,6 @@
> int input_opened;
> int intr_active;
> void (*midi_input_intr) (int dev, unsigned char data);
> + spinlock_t lock;
> } vmidi_devc;
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
prev parent reply other threads:[~2002-09-22 15:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-22 15:37 compile error and fix in v_midi.c Thomas Molina
2002-09-22 15:51 ` Frank Davis [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=3D8DE705.9090907@si.rr.com \
--to=fdavis@si.rr.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tmolina@cox.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