From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Steve Calfee <stevecalfee@gmail.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: git trees
Date: Thu, 31 Mar 2011 09:33:28 +0900 [thread overview]
Message-ID: <20110331003327.GF21487@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <4D93C892.6080602@gmail.com>
On Wed, Mar 30, 2011 at 05:19:30PM -0700, Steve Calfee wrote:
> I am starting to look at a new codec driver. I have been looking at the
> alsa-project wiki describing the various git trees. I am confused
> because they seem to be lagging the linux releases (ie 2.6.38 is out,
> not in the two trees I have tried.
You should be developing against the Linux kernel, not against the out
of tree ALSA, for ASoC. This is mostly true for regular ALSA drivers
too.
> So I checked out origin/for-2.6.39 when i built that I got a kernel
> version 2.6.38-rc1 or something. (and it built but didn't boot)
If it won't boot there's some non-audio issue on your system that you
need to figure out - other than audio it's just straight upstream. For
current work you should use the latest for-2.6.xx branch, currently
2.6.40.
> What I need to know is which tree and which branch or tag I should use
> to develop on and to submit alsa patches from.
Just follow the standard kernel patch submission process as you would
for any other system.
next prev parent reply other threads:[~2011-03-31 0:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-31 0:19 git trees Steve Calfee
2011-03-31 0:33 ` Mark Brown [this message]
2011-03-31 1:03 ` Steve Calfee
2011-03-31 21:39 ` Mark Brown
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=20110331003327.GF21487@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=stevecalfee@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;
as well as URLs for NNTP newsgroup(s).