From: Takashi Iwai <tiwai@suse.de>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: Jesper Andersen <jespera@gmail.com>,
linux-wireless <linux-wireless@vger.kernel.org>,
alsa-devel@alsa-project.org, julia@diku.dk,
linux-kernel@vger.kernel.org
Subject: Re: [alsa-devel] Using spdiff for backporting
Date: Mon, 10 Oct 2011 14:41:05 +0200 [thread overview]
Message-ID: <s5hy5wtxbmm.wl%tiwai@suse.de> (raw)
In-Reply-To: <CAB=NE6X81KPvx-yt33MghmoftUznoP-jYO8sBxoeW_0fzQ1pdA@mail.gmail.com>
At Fri, 7 Oct 2011 10:41:06 -0700,
Luis R. Rodriguez wrote:
>
> > Also, in the slides from the plumbers-conf. I think I saw it mentioned
> > that there's also an alsa-compat git-tree somewhere. Maybe that is a
> > more compelling usecase? I was unable to find it though so I'd
> > appreciate a link.
>
> It was on kernel.org, but if it got rm -rf'd then its gone as I do not
> have a local copy.
Oh, I didn't know of such a tree. So you created alsa driver build
system with your spdiff? That's interesting.
> The compat-alsa stuff though was determined to be
> superflous with the ALSA's team's own backport work which is currently
> independent.
Yes, the external alsa-driver build tree has existed since 10 years
ago :) It was even possible to build with 2.2/2.4 kernels until
recently.
The current tree is found in github,
git://github.com/tiwai/alsa-driver-build.git
> My hope though is to unify these through the compat.git /
> compat-kernel (currently just called compat-wireless) effort.
The common framework would be really nice to have.
V4L also have own build system, and possible other subsystem trees too.
thanks,
Takashi
next prev parent reply other threads:[~2011-10-10 12:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1317721043.11231.2.camel@jmachine>
2011-10-07 17:41 ` Using spdiff for backporting Luis R. Rodriguez
2011-10-10 12:41 ` Takashi Iwai [this message]
2011-10-10 19:30 ` [alsa-devel] " Luis R. Rodriguez
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=s5hy5wtxbmm.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=jespera@gmail.com \
--cc=julia@diku.dk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@gmail.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