From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Steve Calfee <stevecalfee@gmail.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: git trees
Date: Fri, 1 Apr 2011 06:39:17 +0900 [thread overview]
Message-ID: <20110331213915.GA21726@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <4D93D2ED.9040302@gmail.com>
On Wed, Mar 30, 2011 at 06:03:41PM -0700, Steve Calfee wrote:
> Thanks for your time. I was already using linux-next - So that would be
> the correct tree when you say linux kernel?
Follow the generic process covered in Documentation/SubmittingPatches.
> If linux-next is the case how long do I have to wait until some of the
> latest asoc patches arrive? I thought that the alsa trees were somewhat
> ahead of the linux-next because they had asoc/alsa patches in them. For
> instance you have patches against both 2.6.39 and 2.6.40 somewhere and I
> don't think they are in linux-next.
Mostly -next will lag my tree by at most 24 hours. During the period
beween the release of one kernel and the release of the other we don't
put code into -next that isn't intended for -rc1 of the current kernel
in order to help with stabalisation and merge but other than that you
will find the latest ASoC code in -next.
prev parent reply other threads:[~2011-03-31 21:39 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
2011-03-31 1:03 ` Steve Calfee
2011-03-31 21:39 ` Mark Brown [this message]
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=20110331213915.GA21726@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).