From: Ben Skeggs <bskeggs@redhat.com>
To: Andrew Lutomirski <luto@mit.edu>
Cc: stable@kernel.org, dri-devel@lists.freedesktop.org
Subject: Re: [00/66] 2.6.36.1-stable review
Date: Wed, 08 Dec 2010 15:17:20 +1000 [thread overview]
Message-ID: <1291785443.12581.14.camel@nisroch> (raw)
In-Reply-To: <AANLkTi=_qMbwPgN+C+2bctCNim8hLwn_0_NPd4ej7Bp5@mail.gmail.com>
On Sat, 2010-11-20 at 11:15 -0500, Andrew Lutomirski wrote:
> On Sat, Nov 20, 2010 at 10:52 AM, Greg KH <gregkh@suse.de> wrote:
> > On Sat, Nov 20, 2010 at 09:24:05AM -0500, Andy Lutomirski wrote:
> >> Greg KH wrote:
> >>> This is the start of the stable review cycle for the 2.6.36.1 release.
> >>> There are 66 patches in this series, all will be posted as a response
> >>> to this one. If anyone has any issues with these being applied, please
> >>> let us know. If anyone is a maintainer of the proper subsystem, and
> >>> wants to add a Signed-off-by: line to the patch, please respond with it.
> >>
> >> Can you add ab838338a2a9e0cb8346eb0cab9977be13e8dce5? (Somehow the cc:
> >> stable got eaten, but 2.6.36 definitely needs this one. 2.6.35 probably
> >> does as well but I haven't tested it.)
> >
> > Please get an ack from the maintainer of that driver and the drm
> > maintainer so that I can apply it to the next .36 queue.
Acked-by: Ben Skeggs <bskeggs@redhat.com>
> >
>
> Can you ack this for 2.6.36, please?
>
> I suspect that 2.6.35 needs it as well, but I won't be able to test on
> my NV50 machine for two weeks (I'll be out of town, and I don't have
> fancy enough remote control over that box to boot suspected-bad
> kernels remotely).
>
> --Andy
next prev parent reply other threads:[~2010-12-08 5:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20101119220309.GA15562@kroah.com>
[not found] ` <4CE7DA05.8050605@mit.edu>
[not found] ` <20101120155251.GB28803@suse.de>
2010-11-20 16:15 ` [00/66] 2.6.36.1-stable review Andrew Lutomirski
2010-12-08 5:17 ` Ben Skeggs [this message]
2010-12-20 19:44 ` [stable] " 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=1291785443.12581.14.camel@nisroch \
--to=bskeggs@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=luto@mit.edu \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox