From: SF Markus Elfring <elfring@users.sourceforge.net>
To: Takashi Sakamoto <o-takashi@sakamocchi.jp>, alsa-devel@alsa-project.org
Cc: kernel-janitors@vger.kernel.org,
Clemens Ladisch <clemens@ladisch.de>,
Takashi Iwai <tiwai@suse.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: ALSA: bebob: Use common error handling code in snd_bebob_stream_start_duplex()
Date: Wed, 27 Sep 2017 08:38:48 +0200 [thread overview]
Message-ID: <06a8e3ee-c3c3-b4c7-0cf9-69a2efdaf0ba@users.sourceforge.net> (raw)
In-Reply-To: <09bb0e83-01fe-cd12-a084-31db3f12d663@sakamocchi.jp>
> As long as I know, the last product with this solution was shipped
> at 2010. Thus the driver is under maintenance.
Thanks for your information.
> I have some tasks for this driver as well as drivers in ALSA firewire stack,
> however basically this driver is under maintenance and might not get
> further integration.
Good to know in principle …
> I think that code cleanup for the driver don't help the other developers.
I thought in an other direction if other contributors would like to care
for longer term support.
> It's better to apply such cleanup to more long-live codes such as
> core functionality of ALSA.
I am trying another general transformation pattern out.
> In this point of view, whether your patchset is worth to be applied
> or not, Please keep enough time to think about.
Automatic source code analysis can find various update candidates.
I am just unsure if a bit more software development attention is still
appropriate at some places.
Do you find any of the affected software modules so outdated
so that they should not be touched any more?
Regards,
Markus
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next prev parent reply other threads:[~2017-09-27 6:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-06 10:21 [PATCH 0/3] ALSA: BeBoB: Fine-tuning for six function implementations SF Markus Elfring
2017-09-06 10:22 ` [PATCH 1/3] ALSA: bebob: Use common error handling code in snd_bebob_stream_start_duplex() SF Markus Elfring
2017-09-24 3:50 ` Takashi Sakamoto
2017-09-24 7:06 ` SF Markus Elfring
2017-09-26 23:30 ` Takashi Sakamoto
2017-09-27 6:38 ` SF Markus Elfring [this message]
2017-09-27 11:09 ` Takashi Sakamoto
2017-09-06 10:23 ` [PATCH 2/3] ALSA: bebob: Adjust six checks for null pointers SF Markus Elfring
2017-09-06 10:24 ` [PATCH 3/3] ALSA: bebob: Improve a size determination in parse_stream_formation() SF Markus Elfring
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=06a8e3ee-c3c3-b4c7-0cf9-69a2efdaf0ba@users.sourceforge.net \
--to=elfring@users.sourceforge.net \
--cc=alsa-devel@alsa-project.org \
--cc=clemens@ladisch.de \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=o-takashi@sakamocchi.jp \
--cc=tiwai@suse.com \
/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).