Re: [ALSA] AdLib FM card driver
- From: Takashi Iwai <tiwai@xxxxxxx>
- Date: Tue, 28 Mar 2006 12:49:25 +0200
At Mon, 27 Mar 2006 18:29:24 +0200,
Rene Herman wrote:
Rene Herman wrote:
Attached is a version that simply jumps to a return -EINVAL, which
would also be the easiest way to fixup the others, at least for
-stable. If you disagree though, in the next message I'll sent a
version that does register the error, but for now just turns them
into -EINVAL before returning.
As promised. As said, I prefer the previous one. With this one, it would
only be a matter of deleting the "error = -EINVAL;" lines again to have
it propagate the error up after a resolution of that -ENODEV | -ENXIO
thing, but since the value isn't used anyway...
Thanks, it's now in ALSA CVS tree (with a minor modification, error =
-EINVAL is set just before return). It should be propagated to 2.6.17
soon later.
Takashi
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- References:
- [ALSA] AdLib FM card driver
- From: Rene Herman
- Re: [ALSA] AdLib FM card driver
- From: Takashi Iwai
- Re: [ALSA] AdLib FM card driver
- From: Rene Herman
- Re: [ALSA] AdLib FM card driver
- From: Rene Herman
- [ALSA] AdLib FM card driver
- Prev by Date: Re: Fix unlock_buffer() to work the same way as bit_unlock()
- Next by Date: Re: Suspend2-2.2.2 for 2.6.16.
- Previous by thread: Re: [ALSA] AdLib FM card driver
- Next by thread: Re: [Ext2-devel] [PATCH 1/2] ext2/3: Support 2^32-1 blocks(Kernel)
- Index(es):
Relevant Pages
|
|