From: Andy Walls <awalls@md.metrocast.net>
To: Greg KH <greg@kroah.com>, mchehab@redhat.com
Cc: stable@kernel.org, linux-kernel@vger.kernel.org,
linux-media@vger.kernel.org, hverkuil@xs4all.nl, gregkh@suse.de
Subject: Re: [stable] [RESEND][PATCH for stable 2.6.36 REGRESSION] cx25840: Prevent device probe failure due to volume control ERANGE error]
Date: Fri, 10 Dec 2010 14:41:03 -0500 [thread overview]
Message-ID: <1292010063.29254.13.camel@morgan.silverblock.net> (raw)
In-Reply-To: <20101210181630.GA12772@kroah.com>
On Fri, 2010-12-10 at 10:16 -0800, Greg KH wrote:
> On Fri, Dec 10, 2010 at 08:19:57AM -0500, Andy Walls wrote:
> > Resending, since this didn't appear to make its way into in 2.6.36.2.
>
> That's because it's not in Linus's tree, right? I have to wait for that
> to happen before I can add it to a stable tree.
Greg,
I wasn't aware of that constraint in the process, but it makes sense to
me.
Mauro,
My understanding is that the patch has to be in one of your trees first,
and then tested in linux-next for a reasonable length of time, before
Linus will pull it into his tree.
Could you please expedite handling of this patch for 2.6.37:
https://patchwork.kernel.org/patch/376612/
so that the regression can be fixed in 2.6.36?
Regards,
Andy
next prev parent reply other threads:[~2010-12-10 19:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-10 13:19 [RESEND][PATCH for stable 2.6.36 REGRESSION] cx25840: Prevent device probe failure due to volume control ERANGE error] Andy Walls
2010-12-10 18:16 ` [stable] " Greg KH
2010-12-10 19:41 ` Andy Walls [this message]
2010-12-10 20:22 ` Greg KH
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=1292010063.29254.13.camel@morgan.silverblock.net \
--to=awalls@md.metrocast.net \
--cc=greg@kroah.com \
--cc=gregkh@suse.de \
--cc=hverkuil@xs4all.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@redhat.com \
--cc=stable@kernel.org \
/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.