Hello all,
a new ALSA patch for 2.5.4 is available at
ftp://ftp.alsa-project.org/pub/kernel-patches/alsa-2002-02-11-1-linux-2.5.4.patch.gz
I repeat myself but anyway. We are open to any suggestions and
ideas for this kernel integration patch. Unfortunately, Linus has not
approved this directory tree and he is not talking with us at the time.
It seems that BIO changes are over, but he's probably busy enough to
ignore our e-mails with co-operation requests.
Jaroslav
-----
Jaroslav Kysela <[email protected]>
SuSE Linux http://www.suse.com
ALSA Project http://www.alsa-project.org
There are at least 2 reasons that I can see why Linus probably won't
accept your patch:
1. It is not an inline text attachment (it is a URL).
2. It is 79,000 lines long
If you could send the patch in smaller chunks over time, or ask one of
Linus' closer (read Highly Trusted) patch maintainers to apply it to
his/her tree first and get some testing, he might be more inclined to
accept it.
Dan Mann
On Mon, 2002-02-11 at 09:16, Jaroslav Kysela wrote:
> Hello all,
>
> a new ALSA patch for 2.5.4 is available at
>
> ftp://ftp.alsa-project.org/pub/kernel-patches/alsa-2002-02-11-1-linux-2.5.4.patch.gz
>
> I repeat myself but anyway. We are open to any suggestions and
> ideas for this kernel integration patch. Unfortunately, Linus has not
> approved this directory tree and he is not talking with us at the time.
> It seems that BIO changes are over, but he's probably busy enough to
> ignore our e-mails with co-operation requests.
>
> Jaroslav
>
> -----
> Jaroslav Kysela <[email protected]>
> SuSE Linux http://www.suse.com
> ALSA Project http://www.alsa-project.org
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
Dan Mann wrote:
> On Mon, 2002-02-11 at 09:16, Jaroslav Kysela wrote:
> > I repeat myself but anyway. We are open to any suggestions and
> > ideas for this kernel integration patch. Unfortunately, Linus has not
> > approved this directory tree and he is not talking with us at the time.
> > It seems that BIO changes are over, but he's probably busy enough to
> > ignore our e-mails with co-operation requests.
> There are at least 2 reasons that I can see why Linus probably won't
> accept your patch:
>
> 1. It is not an inline text attachment (it is a URL).
> 2. It is 79,000 lines long
Well, merging ALSA is going to be one big mother of a patch no matter
how you slice it :)
But I agree, it would be nice for the patch to be broken up into steps,
ie. first patch moves OSS drivers into new location, second patch adds
infrastructure, third patch adds the 1001 drivers that ALSA supports :)
Also if the ALSA guys wanted to experiment with BK, that would be a
great way to do the merge.
Jeff
--
Jeff Garzik | "I went through my candy like hot oatmeal
Building 1024 | through an internally-buttered weasel."
MandrakeSoft | - goats.com
On 11 Feb 2002, Dan Mann wrote:
>
> There are at least 2 reasons that I can see why Linus probably won't
> accept your patch:
>
> 1. It is not an inline text attachment (it is a URL).
> 2. It is 79,000 lines long
No, both of those are actually ok, I'm not religious about big things like
this if I just feel that they have a good reason for them (and ALSA has a
good reason for being big).
My main reason for being silent on it has been that I've been doing other
things. I'll be merging ALSA in the not too distant future, but it's not
been a high priority for me like some of the other stuff I have spent my
time on..
Linus
I am pretty sure that Linus will not want to be copied on all these emails.
The result is likely to be that he reads none of them.
I don't think that at this stage we should be talking to Linus Torvalds at
all. He is probably too busy.
I think that a much better approach would be to talk to the current kernel
oss sound developers, and get alsa checked into the kernel via them.
I think that one person should be responsible for linux kernel sound, so
that Linus Torvalds does not have to ignore so much email due to overload.
When I have too many emails in my email box, single short(5 lines) emails
get read, whole discussion threads get left unread.
So a simple "Here is the final alsa sound patch for the kernel" from someone
Linus already knows would in my view be more successful.
My 2 cents.
James
> -----Original Message-----
> From: [email protected]
> [mailto:[email protected]]On Behalf Of Jeff Garzik
> Sent: 12 February 2002 00:23
> To: Dan Mann
> Cc: Jaroslav Kysela; ALSA development; LKML; Linus Torvalds
> Subject: [Alsa-devel] Re: ALSA patch for 2.5.4
>
>
> Dan Mann wrote:
> > On Mon, 2002-02-11 at 09:16, Jaroslav Kysela wrote:
> > > I repeat myself but anyway. We are open to any suggestions and
> > > ideas for this kernel integration patch. Unfortunately, Linus has not
> > > approved this directory tree and he is not talking with us at
> the time.
> > > It seems that BIO changes are over, but he's probably busy enough to
> > > ignore our e-mails with co-operation requests.
>
> > There are at least 2 reasons that I can see why Linus probably won't
> > accept your patch:
> >
> > 1. It is not an inline text attachment (it is a URL).
> > 2. It is 79,000 lines long
>
> Well, merging ALSA is going to be one big mother of a patch no matter
> how you slice it :)
>
> But I agree, it would be nice for the patch to be broken up into steps,
> ie. first patch moves OSS drivers into new location, second patch adds
> infrastructure, third patch adds the 1001 drivers that ALSA supports :)
>
> Also if the ALSA guys wanted to experiment with BK, that would be a
> great way to do the merge.
>
> Jeff
>
>
>
> --
> Jeff Garzik | "I went through my candy like hot oatmeal
> Building 1024 | through an internally-buttered weasel."
> MandrakeSoft | - goats.com
>
> _______________________________________________
> Alsa-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/alsa-devel
> I don't think that at this stage we should be talking to Linus Torvalds at
> all. He is probably too busy.
You think too much
> I think that a much better approach would be to talk to the current kernel
> oss sound developers, and get alsa checked into the kernel via them.
Already done - and Linus wants to work directly with them