linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Jan Kara <jack@suse.cz>
To: Sasha Levin <sashal@kernel.org>
Cc: Jan Kara <jack@suse.cz>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-mm@kvack.org, Dan Williams <dan.j.williams@intel.com>,
	stable@vger.kernel.org
Subject: Re: [PATCH] mm: Fix modifying of page protection by insert_pfn()
Date: Mon, 25 Mar 2019 18:02:06 +0100	[thread overview]
Message-ID: <20190325170206.GH8308@quack2.suse.cz> (raw)
In-Reply-To: <20190325003820.EED802147A@mail.kernel.org>

On Mon 25-03-19 00:38:20, Sasha Levin wrote:
> Hi,
> 
> [This is an automated email]
> 
> This commit has been processed because it contains a "Fixes:" tag,
> fixing commit: b2770da64254 mm: add vm_insert_mixed_mkwrite().
> 
> The bot has tested the following trees: v5.0.3, v4.19.30, v4.14.107.
> 
> v5.0.3: Build OK!
> v4.19.30: Failed to apply! Possible dependencies:
>     f2c57d91b0d9 ("mm: Fix warning in insert_pfn()")
> 
> v4.14.107: Failed to apply! Possible dependencies:
>     f2c57d91b0d9 ("mm: Fix warning in insert_pfn()")
> 
> 
> How should we proceed with this patch?

I'd say apply also f2c57d91b0d9 to both trees. Nice automation BTW :).

								Honza
-- 
Jan Kara <jack@suse.com>
SUSE Labs, CR


      reply	other threads:[~2019-03-25 17:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-11  8:45 Jan Kara
2019-03-11 11:59 ` Aneesh Kumar K.V
2019-03-11 17:22 ` Dan Williams
2019-03-27 17:33   ` Jan Kara
2019-03-27 21:14     ` Andrew Morton
2019-03-28  3:18       ` Aneesh Kumar K.V
2019-03-28  9:02         ` Jan Kara
2019-03-28  9:02       ` Jan Kara
2019-03-25  0:38 ` Sasha Levin
2019-03-25 17:02   ` Jan Kara [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=20190325170206.GH8308@quack2.suse.cz \
    --to=jack@suse.cz \
    --cc=akpm@linux-foundation.org \
    --cc=dan.j.williams@intel.com \
    --cc=linux-mm@kvack.org \
    --cc=sashal@kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox