From: Greg KH <greg@kroah.com>
To: Pekka Enberg <penberg@cs.helsinki.fi>
Cc: ngupta@vflare.org, Andrew Morton <akpm@linux-foundation.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ramzswap: remove ARM specific d-cache hack
Date: Mon, 14 Dec 2009 07:18:09 -0800 [thread overview]
Message-ID: <20091214151809.GA16209@kroah.com> (raw)
In-Reply-To: <84144f020912131236m2739aaa5obe6f8399d9e90aea@mail.gmail.com>
On Sun, Dec 13, 2009 at 10:36:26PM +0200, Pekka Enberg wrote:
> On Sun, Dec 13, 2009 at 3:21 AM, Nitin Gupta <ngupta@vflare.org> wrote:
> > On 12/12/2009 01:11 PM, Pekka Enberg wrote:
> >> On Sat, Dec 12, 2009 at 8:14 AM, Nitin Gupta <ngupta@vflare.org> wrote:
> >>> Remove d-cache hack in ramzswap driver that was needed
> >>> to workaround a bug in ARM version of update_mmu_cache()
> >>> which caused stale data in d-cache to be transferred to
> >>> userspace. This bug was fixed by git commit:
> >>> ? ? ? ?787b2faadc4356b6c2c71feb42fb944fece9a12f
> >>> This also brings down one entry in TODO file.
> >>>
> >>> Signed-off-by: Nitin Gupta <ngupta@vflare.org>
> >>
> >> Acked-by: Pekka Enberg <penberg@cs.helsinki.fi>
> >
> > Thanks for review Pekka.
> > Now wondering when this patch will be committed to mainline.
>
> I don't see any reason why this shouldn't go into .33 but that's
> really up to Greg.
It will end up there, thanks, I will queue it up in a few days to go
there.
thanks,
greg k-h
next prev parent reply other threads:[~2009-12-14 15:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-12 6:14 [PATCH] ramzswap: remove ARM specific d-cache hack Nitin Gupta
2009-12-12 7:41 ` Pekka Enberg
2009-12-13 1:21 ` Nitin Gupta
2009-12-13 20:36 ` Pekka Enberg
2009-12-14 15:18 ` Greg KH [this message]
2009-12-18 19:33 ` patch staging-ramzswap-remove-arm-specific-d-cache-hack.patch added to gregkh-2.6 tree gregkh
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=20091214151809.GA16209@kroah.com \
--to=greg@kroah.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ngupta@vflare.org \
--cc=penberg@cs.helsinki.fi \
/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