public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Arnd Bergmann <arnd@arndb•de>
Cc: Heiko Carstens <hca@linux•ibm.com>,
	Vasily Gorbik <gor@linux•ibm.com>,
	Christian Borntraeger <borntraeger@de•ibm.com>,
	Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
	Linux Next Mailing List <linux-next@vger•kernel.org>,
	Nicholas Piggin <npiggin@gmail•com>
Subject: Re: linux-next: manual merge of the s390 tree with the asm-generic tree
Date: Wed, 16 Dec 2020 09:21:17 +1100	[thread overview]
Message-ID: <20201216092117.4f6447d0@canb.auug.org.au> (raw)
In-Reply-To: <20201124102514.0bea1349@canb.auug.org.au>

[-- Attachment #1: Type: text/plain, Size: 2875 bytes --]

Hi all,

On Tue, 24 Nov 2020 10:25:14 +1100 Stephen Rothwell <sfr@canb•auug.org.au> wrote:
>
> Today's linux-next merge of the s390 tree got a conflict in:
> 
>   arch/s390/include/asm/mmu_context.h
> 
> between commit:
> 
>   93e2dfd39438 ("s390: use asm-generic/mmu_context.h for no-op implementations")
> 
> from the asm-generic tree and commits:
> 
>   ab177c5d00cd ("s390/mm: remove unused clear_user_asce()")
>   87d598634521 ("s390/mm: remove set_fs / rework address space handling")
> 
> from the s390 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/mmu_context.h
> index 66f9cf0a07e3,87a84fc59fc3..000000000000
> --- a/arch/s390/include/asm/mmu_context.h
> +++ b/arch/s390/include/asm/mmu_context.h
> @@@ -70,23 -69,8 +70,6 @@@ static inline int init_new_context(stru
>   	return 0;
>   }
>   
> - static inline void set_user_asce(struct mm_struct *mm)
> - {
> - 	S390_lowcore.user_asce = mm->context.asce;
> - 	__ctl_load(S390_lowcore.user_asce, 1, 1);
> - 	clear_cpu_flag(CIF_ASCE_PRIMARY);
> - }
> - 
> - static inline void clear_user_asce(void)
> - {
> - 	S390_lowcore.user_asce = S390_lowcore.kernel_asce;
> - 	__ctl_load(S390_lowcore.kernel_asce, 1, 1);
> - 	set_cpu_flag(CIF_ASCE_PRIMARY);
> - }
> - 
> - mm_segment_t enable_sacf_uaccess(void);
> - void disable_sacf_uaccess(mm_segment_t old_fs);
>  -#define destroy_context(mm)             do { } while (0)
> --
>   static inline void switch_mm(struct mm_struct *prev, struct mm_struct *next,
>   			     struct task_struct *tsk)
>   {
> @@@ -121,18 -98,18 +97,18 @@@ static inline void finish_arch_post_loc
>   		__tlb_flush_mm_lazy(mm);
>   		preempt_enable();
>   	}
> - 	set_fs(current->thread.mm_segment);
> + 	__ctl_load(S390_lowcore.user_asce, 7, 7);
>   }
>   
>  -#define enter_lazy_tlb(mm,tsk)	do { } while (0)
>  -#define deactivate_mm(tsk,mm)	do { } while (0)
>  -
>  +#define activate_mm activate_mm
>   static inline void activate_mm(struct mm_struct *prev,
>                                  struct mm_struct *next)
>   {
>   	switch_mm(prev, next, current);
>   	cpumask_set_cpu(smp_processor_id(), mm_cpumask(next));
> - 	set_user_asce(next);
> + 	__ctl_load(S390_lowcore.user_asce, 7, 7);
>   }
>   
>  +#include <asm-generic/mmu_context.h>
>  +
>   #endif /* __S390_MMU_CONTEXT_H */

This is now a conflict between the asm-generic tree and Linus' tree.

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

      reply	other threads:[~2020-12-15 22:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-23 23:25 linux-next: manual merge of the s390 tree with the asm-generic tree Stephen Rothwell
2020-12-15 22:21 ` Stephen Rothwell [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=20201216092117.4f6447d0@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=arnd@arndb$(echo .)de \
    --cc=borntraeger@de$(echo .)ibm.com \
    --cc=gor@linux$(echo .)ibm.com \
    --cc=hca@linux$(echo .)ibm.com \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=npiggin@gmail$(echo .)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