From: Florian Faber <faber@faberman.de>
To: alsa-devel@alsa-project.org
Subject: Re: [PATCH - [hdspm] RayDAT/AIO 1/2] ALSA: Add support for RME RayDAT and AIO
Date: Thu, 27 Jan 2011 13:19:18 +0100 [thread overview]
Message-ID: <4D4162C6.1050800@faberman.de> (raw)
In-Reply-To: <alpine.LNX.2.00.1101270905430.6272@eeebox2.perex-int.cz>
On 01/27/11 09:09, Jaroslav Kysela wrote:
>> So, simply move these array definitions to hdspm.c.
> I think that the reason is to share these arrays with hdspmixer.
There's more than hdspmixer out there that needs this data.
> But I agree, that it's better to move these static values to .c files.
The solution is to make them non-static (which was an error on my side).
Replicating information is not a bright idea.
Flo
--
Machines can do the work, so people have time to think.
public key 6C002249 x-hkp://wwwkeys.eu.pgp.net
prev parent reply other threads:[~2011-01-27 12:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-26 18:32 [hdspm: Add RME RayDAT/AIO 0/2] Reworked support for RayDAT/AIO Adrian Knoth
2011-01-26 18:32 ` [PATCH - [hdspm] RayDAT/AIO 2/2] ALSA: Add RayDAT and AIO strings to Kconfig Adrian Knoth
[not found] ` <1296066735-11280-2-git-send-email-adi@drcomp.erfurt.thur.de>
2011-01-27 8:04 ` [PATCH - [hdspm] RayDAT/AIO 1/2] ALSA: Add support for RME RayDAT and AIO Takashi Iwai
2011-01-27 8:09 ` Jaroslav Kysela
2011-01-27 10:23 ` [PATCH - hdspm 1/1] ALSA: [hdspm] Move static mapping arrays to .c Adrian Knoth
2011-01-27 10:27 ` [PATCH - [hdspm] RayDAT/AIO 1/2] ALSA: Add support for RME RayDAT and AIO Adrian Knoth
2011-01-27 10:44 ` Jaroslav Kysela
2011-01-27 11:13 ` Takashi Iwai
2011-01-27 12:07 ` Jaroslav Kysela
2011-01-27 11:13 ` Takashi Iwai
2011-01-27 12:19 ` Florian Faber [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=4D4162C6.1050800@faberman.de \
--to=faber@faberman.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.