linux-nvdimm.lists.01.org archive mirror
 help / color / mirror / Atom feed
From: Sasha Levin <sashal-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: Sasha Levin <sashal-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
	Dan Williams
	<dan.j.williams-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
	linux-nvdimm-hn68Rpc1hR1g9hUCZPvPmw@public.gmane.org
Cc: linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	stable-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH 2/2] libnvdimm, pfn: Pad pfn namespaces relative to other regions
Date: Sun, 25 Nov 2018 07:54:09 +0000	[thread overview]
Message-ID: <20181125075410.D0EF220865@mail.kernel.org> (raw)
In-Reply-To: <154308522458.237140.16550557898744466932.stgit-p8uTFz9XbKj2zm6wflaqv1nYeNYlB/vhral2JQCrhuEAvxtiuMwx3w@public.gmane.org>

Hi,

[This is an automated email]

This commit has been processed because it contains a "Fixes:" tag,
fixing commit: cfe30b872058 libnvdimm, pmem: adjust for section collisions with 'System RAM'.

The bot has tested the following trees: v4.19.4, v4.14.83, v4.9.140.

v4.19.4: Build OK!
v4.14.83: Build OK!
v4.9.140: Failed to apply! Possible dependencies:
    Unable to calculate


How should we proceed with this patch?

--
Thanks,
Sasha

  parent reply	other threads:[~2018-11-25  7:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-24 18:46 [PATCH 1/2] tools/testing/nvdimm: Align test resources to 128M Dan Williams
2018-11-24 18:47 ` [PATCH 2/2] libnvdimm, pfn: Pad pfn namespaces relative to other regions Dan Williams
     [not found]   ` <154308522458.237140.16550557898744466932.stgit-p8uTFz9XbKj2zm6wflaqv1nYeNYlB/vhral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2018-11-25  7:54     ` Sasha Levin [this message]
2018-11-25 16:37       ` Dan Williams
2018-12-03 18:37   ` Verma, Vishal L
2018-12-03 18:33 ` [PATCH 1/2] tools/testing/nvdimm: Align test resources to 128M Verma, Vishal L
2018-12-05 22:15 ` [PATCH v2] " Dan Williams

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=20181125075410.D0EF220865@mail.kernel.org \
    --to=sashal-dgejt+ai2ygdnm+yrofe0a@public.gmane.org \
    --cc=dan.j.williams-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-nvdimm-hn68Rpc1hR1g9hUCZPvPmw@public.gmane.org \
    --cc=stable-u79uwXL29TY76Z2rM5mHXA@public.gmane.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;
as well as URLs for NNTP newsgroup(s).