From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: "Harsha, Priya" <priya.harsha@intel.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>
Subject: Re: [PATCH] [RFC 8/13] Intel SST sound card driver
Date: Tue, 11 Aug 2009 11:47:33 +0100 [thread overview]
Message-ID: <20090811104733.GA8221@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <98769532B4BB14429434178695419EAE5F9793FA@bgsmsx501.gar.corp.intel.com>
On Tue, Aug 11, 2009 at 04:13:50PM +0530, Harsha, Priya wrote:
> Can you help me know which component/config file is responsible for
> creation of nodes in /dev/input? What am I missing here?
Normally this is done by either udev or static configuration.
next prev parent reply other threads:[~2009-08-11 10:47 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-03 7:06 [PATCH] [RFC 8/13] Intel SST sound card driver Vinod Koul
2009-07-03 15:16 ` Takashi Iwai
2009-07-07 6:20 ` Harsha, Priya
2009-07-07 6:49 ` Takashi Iwai
2009-07-07 7:04 ` Harsha, Priya
2009-07-07 7:11 ` Takashi Iwai
2009-07-07 7:16 ` Harsha, Priya
2009-07-07 7:26 ` Takashi Iwai
2009-07-08 5:44 ` Harsha, Priya
2009-07-04 10:57 ` Mark Brown
2009-07-07 6:35 ` Harsha, Priya
2009-07-07 11:42 ` Mark Brown
2009-07-08 5:44 ` Harsha, Priya
2009-07-08 9:46 ` Mark Brown
2009-07-17 7:01 ` Harsha, Priya
2009-07-17 10:18 ` Mark Brown
2009-08-01 3:15 ` Harsha, Priya
2009-08-01 9:46 ` Mark Brown
2009-08-03 7:15 ` Harsha, Priya
2009-08-03 10:12 ` Mark Brown
2009-08-03 11:44 ` Harsha, Priya
2009-08-03 11:53 ` Mark Brown
2009-08-10 16:23 ` Harsha, Priya
2009-08-10 16:34 ` Mark Brown
2009-08-11 10:43 ` Harsha, Priya
2009-08-11 10:47 ` Mark Brown [this message]
2009-09-09 12:07 ` control names Harsha, Priya
2009-09-09 12:11 ` Jaroslav Kysela
2009-09-09 12:15 ` Mark Brown
2009-09-09 12:23 ` Harsha, Priya
2009-09-09 12:35 ` Mark Brown
2009-09-11 7:04 ` Harsha, Priya
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=20090811104733.GA8221@rakim.wolfsonmicro.main \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=priya.harsha@intel.com \
/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