alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Adrian Knoth <adi@drcomp.erfurt.thur.de>
To: alsa-devel@alsa-project.org
Subject: Re: [PATCH - [hdspm] 0/3] Support for RME RayDAT and AIO
Date: Tue, 18 Jan 2011 18:06:00 +0100	[thread overview]
Message-ID: <4D35C878.8050507@drcomp.erfurt.thur.de> (raw)
In-Reply-To: <s5hoc7egtxi.wl%tiwai@suse.de>

On 01/18/11 15:36, Takashi Iwai wrote:

Hi!

> Basically one patch should contain the changes that are build-clean,
> i.e. you can build cleanly after patching.  Thus changing a header
> and *.c in separate patches doesn't work well.

Ok. Better luck next time. ;) Speaking of which: should I resend
everything as a whole-in-one patch?

I could also provide a download link (given we're talking 170+kb here)

> Also, please use the generic variable types as much as possible
> for ioctl structs. Avoid use of enum or such, especially ones that
> are typedef'ed. In general, avoid typedefs in the kernel code as much
> as possible. Defining each enum type is no-go.

If've dropped all the new typedefs and only kept the existing ones now.
However, it still reads "enum foo something" in the structs for some
ioctls.

Is this acceptable or do I have to change this to int? If so, would I
manually add a couple of #defines? I somehow feel losing the semantic
connection to the enum is bad, but this might OTOH be intended, e.g. for
the sake of a stable interface.

> Second, don't define arrays in the header file. They must be in the
> body, not included headers.

Cross-checked with hdspmixer and moved to .c, except for the channel
mappings as they're included from userspace. (channel_map*)

> Also, remember checkpatch.pl is your friend.

It already was for the very last days. But I'm more excited about my new
friend Lindent. ;)


Cheers

  reply	other threads:[~2011-01-18 17:06 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-18 14:12 [PATCH - [hdspm] 0/3] Support for RME RayDAT and AIO Adrian Knoth
2011-01-18 14:12 ` [PATCH - [hdspm] 1/3] Add headers for RayDAT and AIO support Adrian Knoth
2011-01-18 14:40   ` Takashi Iwai
2011-01-18 15:00     ` Adrian Knoth
     [not found]     ` <290463D19D2E064191F1F96ECA480A89432873706D@EXMAIL02.scwf.nsc.com>
     [not found]       ` <s5hwrm1l68q.wl%tiwai@suse.de>
2011-01-19  7:20         ` Process of sumit the Audio driver code to ALSA Reddy, MR Swami
2011-01-19  7:36           ` Takashi Iwai
2011-03-07 11:26             ` Reddy, MR Swami
2011-01-19 22:55           ` Seungwhan Youn
2011-01-18 14:12 ` [PATCH - [hdspm] 3/3] Add RayDAT and AIO strings to Kconfig Adrian Knoth
2011-01-18 14:36 ` [PATCH - [hdspm] 0/3] Support for RME RayDAT and AIO Takashi Iwai
2011-01-18 17:06   ` Adrian Knoth [this message]
2011-01-19  6:41     ` Takashi Iwai
     [not found] ` <1295359939-14673-3-git-send-email-adi@drcomp.erfurt.thur.de>
2011-01-18 14:55   ` [PATCH - [hdspm] 2/3] Enable " Takashi Iwai
2011-01-18 15:24     ` Adrian Knoth
2011-01-21  7:07       ` Takashi Iwai

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=4D35C878.8050507@drcomp.erfurt.thur.de \
    --to=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).