linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: mru@kth.se (Måns Rullgård)
To: linux-hotplug@vger.kernel.org
Subject: Re: [PATCH] add sysfs class support for ALSA sound devices [08/10]
Date: Fri, 16 Jan 2004 22:15:58 +0000	[thread overview]
Message-ID: <yw1xu12v7d5t.fsf@kth.se> (raw)
In-Reply-To: <20040115204311.GI22199@kroah.com>

Greg KH <greg@kroah.com> writes:

> This patch adds support for all ALSA sound devices.  The previous OSS
> sound patch is required for this one to work properly.

This doesn't apply cleanly to the latest ALSA (1.0.1).  It's no
problem to do it manually, though.

> diff -Nru a/sound/pci/intel8x0.c b/sound/pci/intel8x0.c
> --- a/sound/pci/intel8x0.c	Thu Jan 15 11:05:58 2004
> +++ b/sound/pci/intel8x0.c	Thu Jan 15 11:05:58 2004
> @@ -2591,6 +2591,7 @@
>  			break;
>  		}
>  	}
> +	card->dev = &pci->dev;

Does this need to be done for all drivers?

-- 
Måns Rullgård
mru@kth.se



-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

  parent reply	other threads:[~2004-01-16 22:15 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-15 20:40 [PATCH] sysfs class patch update [00/10] Greg KH
2004-01-15 20:41 ` [PATCH] add class_simple support [01/10] Greg KH
2004-01-15 20:41   ` [PATCH] add sysfs class support for input devices [02/10] Greg KH
2004-01-15 20:41     ` [PATCH] add class support for lp devices [03/10] Greg KH
2004-01-15 20:41       ` [PATCH] add sysfs class support for mem devices [04/10] Greg KH
2004-01-15 20:42         ` [PATCH] add sysfs class support for misc devices [05/10] Greg KH
2004-01-15 20:42           ` [PATCH] add sysfs class support for raw devices [06/10] Greg KH
2004-01-15 20:42             ` [PATCH] add sysfs class support for OSS sound devices [07/10] Greg KH
2004-01-15 20:43               ` [PATCH] add sysfs class support for ALSA sound devices [08/10] Greg KH
2004-01-15 20:43                 ` [PATCH] clean up sysfs class support for tty devices [09/10] Greg KH
2004-01-15 20:43                   ` [PATCH] add sysfs class support for vc devices [10/10] Greg KH
2004-01-16  4:13                     ` Andrew Morton
     [not found]                       ` <1074279897.23742.754.camel@nosferatu.lan>
2004-01-16 19:17                         ` Andrew Morton
2004-01-16 22:15                 ` Måns Rullgård [this message]
2004-01-17  0:10                   ` [PATCH] add sysfs class support for ALSA sound devices [08/10] Greg KH
2004-01-15 21:23               ` [PATCH] add sysfs class support for OSS sound devices [07/10] Prakash K. Cheemplavam
2004-01-15 21:32                 ` Greg KH
2004-01-20  1:58   ` [PATCH] add class_simple support [01/10] Rusty Russell
2004-01-15 20:57 ` [PATCH] sysfs class patch update [00/10] Måns Rullgård
2004-01-15 22:56   ` Greg KH

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=yw1xu12v7d5t.fsf@kth.se \
    --to=mru@kth.se \
    --cc=linux-hotplug@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;
as well as URLs for NNTP newsgroup(s).