All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rene Herman <rene.herman@keyaccess.nl>
To: Krzysztof Helt <krzysztof.h1@poczta.fm>
Cc: Takashi Iwai <tiwai@suse.de>,
	Alsa-devel <alsa-devel@alsa-project.org>,
	Rene Herman <rene.herman@gmail.com>
Subject: Re: [PATCH 05/11] wss_lib: use wss constants instead of ad1848 ones
Date: Tue, 05 Aug 2008 05:41:21 +0200	[thread overview]
Message-ID: <4897CBE1.8000707@keyaccess.nl> (raw)
In-Reply-To: <20080731210544.4e5ac1de.krzysztof.h1@poczta.fm>

On 31-07-08 21:05, Krzysztof Helt wrote:

> From: Krzysztof Helt <krzysztof.h1@wp.pl>
> 
> Use wss constants for mode.
> Move ad1848 hardware constants to the wss.h.
> Move mixer tlv macros into the ad1848_lib.c from the ad1848.h.
> 
> Signed-off-by: Krzysztof Helt <krzysztof.h1@wp.pl>
> ---
> 
> Changes since previous version:
> 
> 1. No reformatting of switch in the ad1848_lib.c
>    in the snd_ad1848_chip_id() as the file is going
>    to be killed anyway.

Still a little uneasy about the loss of MODE_RUNNING given that the 
original looked as something noone would've added without a specific 
need but I guess we can keep it in mind and match it up with any 
possible regressions.

I _would_ very much like a comment in the changelog about it. It's 
unlikely to be a regression that would be reported quickly with this 
being old hardware generally. Something like:

"Drop the MODE_RUNNING spurious IRQ guard on AD1848 as it doesn not seem 
to be needed."

Otherwise:

Acked-by: Rene Herman <rene.herman@gmail.com>

Rene.

  reply	other threads:[~2008-08-05  3:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-31 19:05 [PATCH 05/11] wss_lib: use wss constants instead of ad1848 ones Krzysztof Helt
2008-08-05  3:41 ` Rene Herman [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-08-05  6:07 krzysztof.h1

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=4897CBE1.8000707@keyaccess.nl \
    --to=rene.herman@keyaccess.nl \
    --cc=alsa-devel@alsa-project.org \
    --cc=krzysztof.h1@poczta.fm \
    --cc=rene.herman@gmail.com \
    --cc=tiwai@suse.de \
    /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.