From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Dan Williams <dan.j.williams@intel•com>,
Michael Ellerman <mpe@ellerman•id.au>,
PowerPC <linuxppc-dev@lists•ozlabs.org>
Cc: Kajol Jain <kjain@linux•ibm.com>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>,
Shivaprasad G Bhat <sbhat@linux•ibm.com>,
Vaibhav Jain <vaibhav@linux•ibm.com>
Subject: linux-next: manual merge of the nvdimm tree with the powerpc tree
Date: Tue, 15 Mar 2022 19:15:38 +1100 [thread overview]
Message-ID: <20220315191538.323eefbb@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1362 bytes --]
Hi all,
Today's linux-next merge of the nvdimm tree got a conflict in:
arch/powerpc/platforms/pseries/papr_scm.c
between commit:
bbbca72352bb ("powerpc/papr_scm: Implement initial support for injecting smart errors")
from the powerpc tree and commit:
4c08d4bbc089 ("powerpc/papr_scm: Add perf interface support")
from the nvdimm tree.
I fixed it up (see below) and can carry the fix as necessary. This
is now fixed as far as linux-next is concerned, but any non trivial
conflicts should be mentioned to your upstream maintainer when your tree
is submitted for merging. You may also want to consider cooperating
with the maintainer of the conflicting tree to minimise any particularly
complex conflicts.
--
Cheers,
Stephen Rothwell
diff --cc arch/powerpc/platforms/pseries/papr_scm.c
index 1238b94b3cc1,4dd513d7c029..000000000000
--- a/arch/powerpc/platforms/pseries/papr_scm.c
+++ b/arch/powerpc/platforms/pseries/papr_scm.c
@@@ -121,9 -124,8 +124,11 @@@ struct papr_scm_priv
/* length of the stat buffer as expected by phyp */
size_t stat_buffer_len;
+ /* The bits which needs to be overridden */
+ u64 health_bitmap_inject_mask;
+
+ /* array to have event_code and stat_id mappings */
+ char **nvdimm_events_map;
};
static int papr_scm_pmem_flush(struct nd_region *nd_region,
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2022-03-15 8:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-15 8:15 Stephen Rothwell [this message]
2022-03-15 11:04 ` linux-next: manual merge of the nvdimm tree with the powerpc tree Michael Ellerman
2022-03-15 14:55 ` Dan Williams
2022-03-15 13:48 ` kajoljain
2022-03-15 17:25 ` Vaibhav Jain
-- strict thread matches above, loose matches on Subject: below --
2018-01-29 6:04 Stephen Rothwell
2018-01-29 22:49 ` Dan Williams
2018-01-29 6:01 Stephen Rothwell
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=20220315191538.323eefbb@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=dan.j.williams@intel$(echo .)com \
--cc=kjain@linux$(echo .)ibm.com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=mpe@ellerman$(echo .)id.au \
--cc=sbhat@linux$(echo .)ibm.com \
--cc=vaibhav@linux$(echo .)ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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