Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1631843 > unrolled thread
| Started by | Stephen Rothwell <sfr@canb.auug.org.au> |
|---|---|
| First post | 2017-04-27 05:30 +0200 |
| Last post | 2017-04-27 08:50 +0200 |
| Articles | 2 — 2 participants |
Back to article view | Back to linux.kernel
linux-next: manual merge of the kvms390 tree with the s390 tree Stephen Rothwell <sfr@canb.auug.org.au> - 2017-04-27 05:30 +0200
Re: linux-next: manual merge of the kvms390 tree with the s390 tree Christian Borntraeger <borntraeger@de.ibm.com> - 2017-04-27 08:50 +0200
| From | Stephen Rothwell <sfr@canb.auug.org.au> |
|---|---|
| Date | 2017-04-27 05:30 +0200 |
| Subject | linux-next: manual merge of the kvms390 tree with the s390 tree |
| Message-ID | <tAIhX-37Y-5@gated-at.bofh.it> |
Hi all,
Today's linux-next merge of the kvms390 tree got a conflict in:
arch/s390/include/asm/cpacf.h
between commit:
985a9d20daa6 ("s390/crypto: Renaming PPNO to PRNO.")
from the s390 tree and commit:
152c1c8d60eb ("s390/cpacf: Introduce kma instruction")
from the kvms390 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/s390/include/asm/cpacf.h
index 7707a35176c4,31cac7d17b48..000000000000
--- a/arch/s390/include/asm/cpacf.h
+++ b/arch/s390/include/asm/cpacf.h
@@@ -25,7 -25,8 +25,8 @@@
#define CPACF_KMO 0xb92b /* MSA4 */
#define CPACF_PCC 0xb92c /* MSA4 */
#define CPACF_KMCTR 0xb92d /* MSA4 */
-#define CPACF_PPNO 0xb93c /* MSA5 */
+#define CPACF_PRNO 0xb93c /* MSA5 */
+ #define CPACF_KMA 0xb929 /* MSA8 */
/*
* En/decryption modifier bits
[toc] | [next] | [standalone]
| From | Christian Borntraeger <borntraeger@de.ibm.com> |
|---|---|
| Date | 2017-04-27 08:50 +0200 |
| Message-ID | <tALpv-5dO-7@gated-at.bofh.it> |
| In reply to | #1631843 |
On 04/27/2017 05:29 AM, Stephen Rothwell wrote:
> Hi all,
>
> Today's linux-next merge of the kvms390 tree got a conflict in:
>
> arch/s390/include/asm/cpacf.h
>
> between commit:
>
> 985a9d20daa6 ("s390/crypto: Renaming PPNO to PRNO.")
>
> from the s390 tree and commit:
>
> 152c1c8d60eb ("s390/cpacf: Introduce kma instruction")
>
> from the kvms390 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.
>
Correct fix, thanks. It should be ok again tomorrow as Martin has merged
my topic branch.
[toc] | [prev] | [standalone]
Back to top | Article view | linux.kernel
csiph-web