From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: ASoC updates
Date: Mon, 5 Jan 2009 21:09:18 +0000 [thread overview]
Message-ID: <20090105210918.GA21839@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <s5hocylpj9a.wl%tiwai@suse.de>
On Mon, Jan 05, 2009 at 09:53:21PM +0100, Takashi Iwai wrote:
> Are all these 2.6.30 material or for 2.6.29?
They're a bit on the edge, I'd expect them to be safe for 2.6.29 but the
conservative thing would be to punt to 2.6.30. None of them are
critical.
> For 2.6.30, I'll create another branch. It won't be included in
> linux-next, too, until rc1 is reached (Stephen requested so), but we
> can keep it in our main branch, of course.
How about branching off a fixes branch for 2.6.29 rather than a -next
branch? That way we can keep using the same branch for further fixes
through the -rc series. Doesn't make much difference either way,
though.
next prev parent reply other threads:[~2009-01-05 21:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-05 17:56 ASoC updates Mark Brown
2009-01-05 20:53 ` Takashi Iwai
2009-01-05 21:09 ` Mark Brown [this message]
2009-01-06 8:45 ` Takashi Iwai
-- strict thread matches above, loose matches on Subject: below --
2009-01-27 20:03 Mark Brown
2009-01-28 8:11 ` Takashi Iwai
2008-12-19 14:08 [PATCHv2 1/1] Fix a Oops bug in omap soc driver Stanley.Miao
2008-12-19 14:35 ` Jarkko Nikula
2008-12-19 14:39 ` [alsa-devel] " Takashi Iwai
2008-12-20 13:51 ` ASoC updates Mark Brown
2008-12-20 14:11 ` SUBHRANIL CHOUDHURY
2008-12-20 14:58 ` Sean McNamara
2008-12-20 15:47 ` Takashi Iwai
2008-10-10 14:51 Mark Brown
2008-10-11 15:34 ` Takashi Iwai
2008-10-02 10:02 Mark Brown
2008-10-02 10:36 ` Takashi Iwai
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=20090105210918.GA21839@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=tiwai@suse.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.