From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
Cc: akpm@linux-foundation.org, sergey.senozhatsky@gmail.com,
minchan@kernel.org, ngupta@vflare.org,
mm-commits@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-next@vger.kernel.org, Heesub Shin <heesub.shin@samsung.com>
Subject: Re: + zsmalloc-do-not-remap-dst-page-while-prepare-next-src-page.patch added to -mm tree
Date: Wed, 25 Mar 2015 17:49:38 +1100 [thread overview]
Message-ID: <20150325174938.3d05eb8a@canb.auug.org.au> (raw)
In-Reply-To: <20150325054230.GB1675@swordfish>
[-- Attachment #1: Type: text/plain, Size: 946 bytes --]
Hi Sergey,
On Wed, 25 Mar 2015 14:42:30 +0900 Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com> wrote:
>
> On (03/24/15 14:03), akpm@linux-foundation.org wrote:
> > The patch titled
> > Subject: zsmalloc: do not remap dst page while prepare next src page
> > has been added to the -mm tree. Its filename is
> > zsmalloc-do-not-remap-dst-page-while-prepare-next-src-page.patch
> >
> > This patch should soon appear at
> > http://ozlabs.org/~akpm/mmots/broken-out/zsmalloc-do-not-remap-dst-page-while-prepare-next-src-page.patch
> > and later at
> > http://ozlabs.org/~akpm/mmotm/broken-out/zsmalloc-do-not-remap-dst-page-while-prepare-next-src-page.patch
> >
>
> Heesub Shin has reported that this patch causes BUG_ON on ARM
> (with CONFIG_DEBUG_HIGHMEM enabled). Could you please revert
> it in linux-next 20150325?
Done.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2015-03-25 6:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5511d133.CLvN99GLSL/edQEW%akpm@linux-foundation.org>
2015-03-25 5:42 ` + zsmalloc-do-not-remap-dst-page-while-prepare-next-src-page.patch added to -mm tree Sergey Senozhatsky
2015-03-25 6:49 ` Stephen Rothwell [this message]
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=20150325174938.3d05eb8a@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=akpm@linux-foundation.org \
--cc=heesub.shin@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=minchan@kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=ngupta@vflare.org \
--cc=sergey.senozhatsky.work@gmail.com \
--cc=sergey.senozhatsky@gmail.com \
/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