From: Jiri Slaby <jirislaby@gmail.com>
To: Eric Paris <eparis@redhat.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Al Viro <viro@zeniv.linux.org.uk>, Takashi Iwai <tiwai@suse.de>,
Pekka Enberg <penberg@kernel.org>, Thomas Meyer <thomas@m3y3r.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Valdis.Kletnieks@vt.edu
Subject: Re: 2.6.36: Sound stop working
Date: Fri, 13 Aug 2010 09:50:00 +0200 [thread overview]
Message-ID: <4C64F928.7030305@gmail.com> (raw)
In-Reply-To: <1281664431.2996.60.camel@dhcp231-200.rdu.redhat.com>
On 08/13/2010 03:53 AM, Eric Paris wrote:
> I guess noone (including me) is testing sound in linux-next :(.
Yeah, there are some people like Valdis and me who run -next based
kernels (-mm). But it got upstream too fast to react earlier. I updated
to the latest -next few days ago, Valdis with the latest mmotm release 2
days ago. So I think these things need to sit in -next a bit longer than
they usually do. The reason is also that I need to solve 2-3 issues with
every -next update and it takes time too.
regards,
--
js
next prev parent reply other threads:[~2010-08-13 7:50 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-12 20:00 2.6.36: Sound stop working Thomas Meyer
2010-08-12 20:10 ` Pekka Enberg
2010-08-12 20:20 ` Linus Torvalds
2010-08-12 21:01 ` Linus Torvalds
2010-08-12 20:26 ` Takashi Iwai
2010-08-12 21:01 ` Jiri Slaby
2010-08-12 21:14 ` Maxim Levitsky
2010-08-12 21:17 ` Takashi Iwai
2010-08-12 21:41 ` Linus Torvalds
2010-08-12 21:50 ` Linus Torvalds
2010-08-12 21:52 ` Al Viro
2010-08-12 22:19 ` Linus Torvalds
2010-08-13 1:53 ` Eric Paris
2010-08-13 7:50 ` Jiri Slaby [this message]
2010-08-12 22:07 ` Takashi Iwai
2010-08-12 21:18 ` Linus Torvalds
2010-08-12 21:24 ` Jiri Slaby
2010-08-12 21:45 ` 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=4C64F928.7030305@gmail.com \
--to=jirislaby@gmail.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=eparis@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=penberg@kernel.org \
--cc=thomas@m3y3r.de \
--cc=tiwai@suse.de \
--cc=torvalds@linux-foundation.org \
--cc=viro@zeniv.linux.org.uk \
/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