From: Clemens Ladisch <clemens@ladisch.de>
To: alsa-devel@alsa-project.org
Subject: Re: Hardware-specific IOCTLs
Date: Tue, 17 Jan 2012 23:02:05 +0100 [thread overview]
Message-ID: <4F15EFDD.5010008@ladisch.de> (raw)
In-Reply-To: <1326494746.63666.YahooMailNeo@web121805.mail.ne1.yahoo.com>
Ivan Bublikov wrote:
>> Ivan Bublikov wrote:
>>> My difficulty is how to define a code for my IOCTL and avoid
>>> a conflict with the common code in the future.
>>
>> Pick something not yet allocated in Documentation/ioctl/ioctl-number.txt.
>
> Since half of the lines in it are marked "Conflict!" anyway, should
> I only pay attention to not conflict with "sound/*" lines?
There are enough free codes so that you do not need to introduce new
conflicts.
> And then add a new line for my IOCTLs?
Yes.
> And should I put my IOCTL definitions in hda_hwdep.h or create a new
> file?
If you go through the existing HDA hwdep device, your ioctls probably
should go into the same header.
Regards,
Clemens
prev parent reply other threads:[~2012-01-17 22:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-13 16:22 Hardware-specific IOCTLs Ivan Bublikov
2012-01-13 17:31 ` Clemens Ladisch
2012-01-13 22:45 ` Ivan Bublikov
2012-01-17 22:02 ` Clemens Ladisch [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=4F15EFDD.5010008@ladisch.de \
--to=clemens@ladisch.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.