alsa-asoc-devel?

alsa-asoc-devel?

[David Henningsson]

Hi,

There is a lot of asoc traffic on this list, and I assume many people
following this list are not interested in ASoC patches.

Have you considered splitting the alsa-devel mailing list into an
alsa-asoc-devel mailing list, for ASoC specific stuff, and alsa-devel
for everything else?

-- 
David Henningsson, Canonical Ltd.
http://launchpad.net/~diwic

Re: alsa-asoc-devel?

[Liam Girdwood]

On Fri, 2010-08-06 at 10:38 +0200, David Henningsson wrote:
> Hi,
> 
> There is a lot of asoc traffic on this list, and I assume many people
> following this list are not interested in ASoC patches.
> 
> Have you considered splitting the alsa-devel mailing list into an
> alsa-asoc-devel mailing list, for ASoC specific stuff, and alsa-devel
> for everything else?
> 

IMO, I think it's pretty much fine where it is atm. It's easy enough to
filter the posts between ASoC, HDA, OSS etc if you are interested in a
particular area. Moving the list would also mean core ALSA changes may
not be fully discussed by ASoC developers/users etc.

Liam
-- 
Freelance Developer, SlimLogic Ltd
ASoC and Voltage Regulator Maintainer.
http://www.slimlogic.co.uk

Re: alsa-asoc-devel?

[David Henningsson]

2010-08-06 12:48, Liam Girdwood skrev:
> On Fri, 2010-08-06 at 10:38 +0200, David Henningsson wrote:
>> Hi,
>>
>> There is a lot of asoc traffic on this list, and I assume many people
>> following this list are not interested in ASoC patches.
>>
>> Have you considered splitting the alsa-devel mailing list into an
>> alsa-asoc-devel mailing list, for ASoC specific stuff, and alsa-devel
>> for everything else?
> 
> IMO, I think it's pretty much fine where it is atm. It's easy enough to
> filter the posts between ASoC, HDA, OSS etc if you are interested in a
> particular area. Moving the list would also mean core ALSA changes may
> not be fully discussed by ASoC developers/users etc.

I'm not saying ASoC developers and users should stop subscribing to
alsa-devel, if they want to know about core ALSA changes.

Also, filtering is easy enough for local mailboxes, but not for people
following the list via gmane.org, or when looking through alsa-devel's
archives.

Let's hear if more people has something to say about this proposal. If
I'm the only one thinking that a split would be good, obviously it
should stay the way it is :-)

-- 
David Henningsson, Canonical Ltd.
http://launchpad.net/~diwic

Re: alsa-asoc-devel?

[Timur Tabi]

On Friday, August 6, 2010, David Henningsson
<david.henningsson@canonical.com> wrote:
> 2010-08-06 12:48, Liam Girdwood skrev:

> Let's hear if more people has something to say about this proposal. If
> I'm the only one thinking that a split would be good, obviously it
> should stay the way it is :-)

I'm pretty sure that anyone who works on ASOC drivers would be opposed
to a split.  Sometimes it's hard to know whether a problem I'm having
is because of asoc or alsa.

My vote is against splitting.


-- 
Timur Tabi
Linux kernel developer at Freescale

Re: alsa-asoc-devel?

[Mark Brown]

On Fri, Aug 06, 2010 at 10:38:01AM +0200, David Henningsson wrote:

> There is a lot of asoc traffic on this list, and I assume many people
> following this list are not interested in ASoC patches.

> Have you considered splitting the alsa-devel mailing list into an
> alsa-asoc-devel mailing list, for ASoC specific stuff, and alsa-devel
> for everything else?

I don't think that's going to be particularly useful, you could say much
the same thing for all these HDA patches that people insist on posting :) .
The overwhelming majority of the traffic on this list is in some way
driver specific so trying to split it up would just result in one list
per driver and reduce the level of cross fertilisation of ideas about
how to approach things.

I certainly find the information I pick up from non-ASoC discussions
useful.

Re: alsa-asoc-devel?

[Mark Brown]

On Fri, Aug 06, 2010 at 10:38:01AM +0200, David Henningsson wrote:

> There is a lot of asoc traffic on this list, and I assume many people
> following this list are not interested in ASoC patches.

Oh, and please also remember to CC maintainers on mails.  This is a
basic thing which applies to pretty much all kernel related lists.