From: Greg KH <gregkh@linuxfoundation.org>
To: Jonathan Morton <jonathan.morton@movial.com>
Cc: stable@vger.kernel.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] ttm_get_pages() will OOPS with highmem allocation
Date: Fri, 16 Nov 2012 09:32:37 -0800 [thread overview]
Message-ID: <20121116173237.GA31589@kroah.com> (raw)
In-Reply-To: <20121116191901.22b3e11c@sd070>
On Fri, Nov 16, 2012 at 07:19:01PM +0200, Jonathan Morton wrote:
> Reposting from this kernel bug:
> https://bugzilla.kernel.org/show_bug.cgi?id=50241
>
> I've tested the patch and it solves a highly repeatable OOPS with the
> CedarView driver that I'm porting.
>
> Reviewed-by: Thomas Hellstrom <thellstrom@vmware.com>
<formletter>
This is not the correct way to submit patches for inclusion in the
stable kernel tree. Please read Documentation/stable_kernel_rules.txt
for how to do this properly.
</formletter>
next prev parent reply other threads:[~2012-11-16 17:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-16 17:19 [PATCH] ttm_get_pages() will OOPS with highmem allocation Jonathan Morton
2012-11-16 17:32 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-11-13 18:31 Jonathan Morton
2012-11-14 8:48 ` Thomas Hellstrom
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=20121116173237.GA31589@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=jonathan.morton@movial.com \
--cc=stable@vger.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.