public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>,
	"H. Peter Anvin" <hpa@zytor.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Martin Schwidefsky <schwidefsky@de.ibm.com>,
	Heiko Carstens <heiko.carstens@de.ibm.com>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: linux-next: manual merge of the tip tree with the s390 tree
Date: Thu, 20 Aug 2015 15:32:38 +1000	[thread overview]
Message-ID: <20150820153238.673130bb@canb.auug.org.au> (raw)

Hi all,

Today's linux-next merge of the tip tree got a conflict in:

  arch/s390/lib/uaccess.c

between commit:

  cabc4abe8e36 ("s390/uaccess: remove uaccess_primary kernel parameter")

from the s390 tree and commit:

  ed79e946732e ("s390/uaccess, locking/static_keys: employ static_branch_likely()")

from the tip tree.

I fixed it up (see below) and can carry the fix as necessary (no action
is required).

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

diff --cc arch/s390/lib/uaccess.c
index 0d002a746bec,93cb1d09493d..000000000000
--- a/arch/s390/lib/uaccess.c
+++ b/arch/s390/lib/uaccess.c
@@@ -370,10 -370,23 +370,10 @@@ long __strncpy_from_user(char *dst, con
  }
  EXPORT_SYMBOL(__strncpy_from_user);
  
 -/*
 - * The "old" uaccess variant without mvcos can be enforced with the
 - * uaccess_primary kernel parameter. This is mainly for debugging purposes.
 - */
 -static int uaccess_primary __initdata;
 -
 -static int __init parse_uaccess_pt(char *__unused)
 -{
 -	uaccess_primary = 1;
 -	return 0;
 -}
 -early_param("uaccess_primary", parse_uaccess_pt);
 -
  static int __init uaccess_init(void)
  {
 -	if (!uaccess_primary && test_facility(27))
 +	if (test_facility(27))
- 		static_key_slow_inc(&have_mvcos);
+ 		static_branch_enable(&have_mvcos);
  	return 0;
  }
  early_initcall(uaccess_init);

             reply	other threads:[~2015-08-20  5:32 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-20  5:32 Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-03-19  4:54 linux-next: manual merge of the tip tree with the s390 tree Stephen Rothwell
2025-03-19 19:50 ` Ingo Molnar
2025-03-28 14:16   ` Joel Granados
2025-03-26  1:28 ` Stephen Rothwell
2023-04-18 13:40 broonie
2023-02-10  1:00 Stephen Rothwell
2023-02-21 23:03 ` Stephen Rothwell
2019-05-06  6:58 Stephen Rothwell
2017-11-01  6:04 Stephen Rothwell
2017-10-11 15:51 Mark Brown
2017-11-13  5:30 ` Stephen Rothwell
2013-02-07  2:50 Stephen Rothwell
2012-03-14  3:46 Stephen Rothwell
2009-08-24  7:01 Stephen Rothwell
2009-08-24  8:17 ` Heiko Carstens
2009-08-24  8:23   ` Stephen Rothwell
2009-08-24  8:53   ` Ingo Molnar

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=20150820153238.673130bb@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=heiko.carstens@de.ibm.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=peterz@infradead.org \
    --cc=schwidefsky@de.ibm.com \
    --cc=tglx@linutronix.de \
    /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