public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Huang Ying <ying.huang@intel.com>
Cc: Ebru Akagunduz <ebru.akagunduz@gmail.com>,
	LKML <linux-kernel@vger.kernel.org>, LKP ML <lkp@01.org>
Subject: Re: [LKP] [mm] 7d5b506f3c2: -3.9% pigz.time.minor_page_faults
Date: Thu, 12 Feb 2015 12:58:03 +1100	[thread overview]
Message-ID: <20150212125803.47c19fa4@canb.auug.org.au> (raw)
In-Reply-To: <1423704926.5968.117.camel@intel.com>

[-- Attachment #1: Type: text/plain, Size: 849 bytes --]

Hi Huang,

On Thu, 12 Feb 2015 09:35:26 +0800 Huang Ying <ying.huang@intel.com> wrote:
>
> FYI, we noticed the below changes on
> 
> git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> commit 7d5b506f3c295ff81e34235544a9e6ac143743c1 ("mm: incorporate read-only pages into transparent huge pages")

You may need to be more precise about the tree that you are using as
linux-next rebases every day and so there could be different
interactions with a single commit depending on what else is in a
particular release.  For example, the above commit appears in 4
different linux-next releases so far (next-20150204, next-20150209,
next-20150210, next-20150211).

Also, mm related problems should probably also be reported to Andrew
Morton.

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

      reply	other threads:[~2015-02-12  1:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-12  1:35 [LKP] [mm] 7d5b506f3c2: -3.9% pigz.time.minor_page_faults Huang Ying
2015-02-12  1:58 ` 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=20150212125803.47c19fa4@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=ebru.akagunduz@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@01.org \
    --cc=ying.huang@intel.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