Alsa-Devel Archive on 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>
Subject: Re: [PATCH 10/10] wss_lib: use wss detection code instead of ad1848 one
Date: Thu, 24 Jul 2008 11:31:00 +0200	[thread overview]
Message-ID: <48884BD4.3010308@keyaccess.nl> (raw)
In-Reply-To: <20080724072620.4197510c.krzysztof.h1@poczta.fm>

On 24-07-08 07:26, Krzysztof Helt wrote:

>>> diff --git a/sound/isa/ad1848/ad1848.c b/sound/isa/ad1848/ad1848.c
>>> index 5f5271e..3500548 100644
>>> --- a/sound/isa/ad1848/ad1848.c
>>> +++ b/sound/isa/ad1848/ad1848.c
>>> @@ -70,15 +70,15 @@ static int __devinit snd_ad1848_match(struct device *dev, unsigned int n)
>>>                 return 0;
>>>  
>>>         if (port[n] == SNDRV_AUTO_PORT) {
>>> -               snd_printk(KERN_ERR "%s: please specify port\n", dev->bus_id);
>>> +               snd_printk(KERN_ERR "%s: please specify port\n", dev_name(dev));
>>>                 return 0;
>>>         }
>> The comment in dev_name() makes me wonder a bit but I guess we'll deal 
>> with it then if there's anything to deal with.
> 
> This is not my change. It is probably diff between some -mm kernel
> version and alsa-driver. It should not be there as the ad1848.c is
> going to be deleted.

I see. It's definitely from the patch you sent though:

http://mailman.alsa-project.org/pipermail/alsa-devel/2008-July/008978.html

>>> -CS4236_DOUBLE("Master Digital Playback Switch", 0, CS4236_LEFT_MASTER, CS4236_RIGHT_MASTER, 7, 7, 1, 1),
>>> -CS4236_DOUBLE("Master Digital Capture Switch", 0, CS4236_DAC_MUTE, CS4236_DAC_MUTE, 7, 6, 1, 1),
>>> +CS4236_DOUBLE("Master Digital Playback Switch", 0,
>>> +               CS4236_LEFT_MASTER, CS4236_RIGHT_MASTER, 7, 7, 1, 1),
>>> +CS4236_DOUBLE("Master Digital Capture Switch", 0,
>>> +               CS4236_DAC_MUTE, CS4236_DAC_MUTE, 7, 6, 1, 1),
>> I can't say I'm personally a fan of these kinds of changes. The point of 
>> them would supposedly be to make the code more readable but as far as I 
>> am concerned it does the reverse.
>>
>> I know that Takashi can be an 80-column fundamentalist so I'll not 
>> object I guess. I'd personally like these (all) restored to a single 
>> line but if he doesn't, so be it.
> 
> Exactly. It was done for Takashi.

Yes, he overrides. I'd try to get away with just saying no though. That 
checkpatch thing desperately needs a clue.

>>> +static void snd_wss_playback_format(struct snd_wss *chip,
>> [ ... ]
>>
>>> -                       snd_cs4231_out(chip, CS4231_PLAYBK_FORMAT, chip->image[CS4231_PLAYBK_FORMAT] = pdfr);
>>> +                       chip->image[CS4231_PLAYBK_FORMAT] = pdfr;
>>> +                       snd_wss_out(chip, CS4231_ALT_FEATURE_1,
>>> +                                   chip->image[CS4231_ALT_FEATURE_1] &= ~0x10);

Oh, missed commenting on this assignment-in-argument due to commenting 
on the other one...

>> As long as you're at it... could you split this assignment same as you 
>> did above?
>>
> 
> Ok. I did it above because otherwise the line was too long ...

Okay. Style-consistency really is fairly important. Otherwise you each 
time have to "retrain" while reading code. In that sense, even leaving 
them all in would/can be better than some in, some out although in this 
case "all out" is quite preffered.

(I only looked at the patch itself though -- if there are many more of 
these than leaving them in and (perhaps) fixing it in a follow-up might 
be preferred).

>> Right-o. That was a 4000+ line patch and I ran out of evening. Rest will 
>> have to wait for tomorrow then. If you make changes, could you very 
>> specifically indicate those changes so that I might be able to get away 
>> with not reading the entire thing again? :-/
> 
> Yes.

Thank you :-)

Rene.

  reply	other threads:[~2008-07-24  9:28 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-18 19:51 [PATCH 10/10] wss_lib: use wss detection code instead of ad1848 one Krzysztof Helt
2008-07-20 16:09 ` Rene Herman
2008-07-23 21:28   ` Rene Herman
2008-07-24  5:26     ` Krzysztof Helt
2008-07-24  9:31       ` Rene Herman [this message]
2008-07-28 15:37         ` Takashi Iwai
2008-07-28 18:39           ` Rene Herman
2008-07-29 13:02             ` Takashi Iwai
2008-07-29 14:15               ` Rene Herman
2008-07-29 14:31                 ` Takashi Iwai
2008-07-29 14:37                   ` Rene Herman
2008-07-29 18:53                   ` Krzysztof Helt
2008-07-29 19:00                     ` Rene Herman
2008-07-24 17:19       ` Rene Herman
2008-07-24 18:47         ` Krzysztof Helt
2008-07-24 19:30           ` Rene Herman
2008-07-24 20:05             ` Rene Herman
2008-07-24 21:41             ` Krzysztof Helt
2008-07-25  9:59               ` Rene Herman
2008-08-04  1:47             ` Rene Herman
2008-08-04  4:31               ` Krzysztof Helt
  -- strict thread matches above, loose matches on Subject: below --
2008-07-25 13:39 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=48884BD4.3010308@keyaccess.nl \
    --to=rene.herman@keyaccess.nl \
    --cc=alsa-devel@alsa-project.org \
    --cc=krzysztof.h1@poczta.fm \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox