From: "Jörn Nettingsmeier" <nettings@stackingdwarves.net>
To: alsa-devel@alsa-project.org, Adrian Knoth <adi@drcomp.erfurt.thur.de>
Subject: [PATCH] hdspm.c: make driver name generic to avoid user confusion
Date: Tue, 07 Jun 2011 10:48:28 +0200 [thread overview]
Message-ID: <4DEDE5DC.40206@stackingdwarves.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 561 bytes --]
hi adi, *!
here's a trivial patch to change the driver name of hdspm.c to avoid
irritating users who don't have the MADI version (just happened on the
LAU list).
iiuc, no external software should make any assumptions about this
string, so there should be no side effects, but i have been wrong before :)
please review and apply.
best,
jörn
--
Jörn Nettingsmeier
Lortzingstr. 11, 45128 Essen, Tel. +49 177 7937487
Meister für Veranstaltungstechnik (Bühne/Studio)
Tonmeister (VDT)
http://stackingdwarves.net
[-- Attachment #2: hdspm-driver-name.diff --]
[-- Type: text/x-patch, Size: 406 bytes --]
--- linux-2.6.39/sound/pci/rme9652/hdspm.c.orig 2011-05-19 06:06:34.000000000 +0200
+++ linux-2.6.39/sound/pci/rme9652/hdspm.c 2011-06-07 10:37:21.894932961 +0200
@@ -6775,7 +6775,7 @@
}
static struct pci_driver driver = {
- .name = "RME Hammerfall DSP MADI",
+ .name = "RME Hammerfall HDSPe Series",
.id_table = snd_hdspm_ids,
.probe = snd_hdspm_probe,
.remove = __devexit_p(snd_hdspm_remove),
[-- Attachment #3: Type: text/plain, Size: 0 bytes --]
next reply other threads:[~2011-06-07 8:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-07 8:48 Jörn Nettingsmeier [this message]
[not found] <4DEDE4E2.4060303@folkwang-hochschule.de>
2011-06-07 9:11 ` [PATCH] hdspm.c: make driver name generic to avoid user confusion Adrian Knoth
2011-06-07 10:39 ` Takashi Iwai
2011-06-07 12:13 ` Takashi Iwai
2011-06-14 7:00 ` Takashi Iwai
2011-06-07 10:46 ` Jörn Nettingsmeier
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=4DEDE5DC.40206@stackingdwarves.net \
--to=nettings@stackingdwarves.net \
--cc=adi@drcomp.erfurt.thur.de \
--cc=alsa-devel@alsa-project.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).