[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d5573b12-7e52-7f62-11b4-07558152eed2@users.sourceforge.net>
Date: Tue, 28 Nov 2017 14:10:53 +0100
From: SF Markus Elfring <elfring@...rs.sourceforge.net>
To: Ondrej Zary <linux@...nbow-software.org>,
alsa-devel@...a-project.org
Cc: Takashi Iwai <tiwai@...e.de>,
Arvind Yadav <arvind.yadav.cs@...il.com>,
Takashi Sakamoto <o-takashi@...amocchi.jp>,
kernel-janitors@...r.kernel.org,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: [alsa-devel] ALSA: nm256: Fine-tuning for three function
implementations
>> Can you get the impression that the shown transformation patterns were
>> correctly applied for the source file “sound/pci/nm256/nm256.c”?
>
> Have you tested the driver?
Which results do you expect from a corresponding system test?
> Please don't "improve" working drivers unless
I am trying to improve software components also for devices to which
I have not got direct access so far.
> Patches like this are known to cause regressions.
Do you prefer to keep this software area “frozen” anyhow?
> If the hardware is rare (like the NM256), the regression can hit years later
> when someone with such HW upgrades distro (e.g. Debian stable).
Have you got any resources to reduce corresponding concerns?
Regards,
Markus
Powered by blists - more mailing lists