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>, Andrew Morton <akpm@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: manual merge of the asm-generic tree with the mm tree
Date: Thu, 11 Jan 2024 09:22:46 +1100	[thread overview]
Message-ID: <20240111092246.10ba37af@canb.auug.org.au> (raw)
In-Reply-To: <20231205090546.7dffe3aa@canb.auug.org.au>

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

Hi all,

On Tue, 5 Dec 2023 09:05:46 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> 
> Today's linux-next merge of the asm-generic tree got a conflict in:
> 
>   arch/mips/include/asm/traps.h
> 
> between commit:
> 
>   6b281b05cbcc ("mips: add missing declarations for trap handlers")
> 
> from the mm tree and commit:
> 
>   23f8c1823bd4 ("arch: add do_page_fault prototypes")
> 
> from the asm-generic tree.
> 
> 
> diff --cc arch/mips/include/asm/traps.h
> index 2c2b26f1e464,d4d9f8a8fdea..000000000000
> --- a/arch/mips/include/asm/traps.h
> +++ b/arch/mips/include/asm/traps.h
> @@@ -39,28 -39,7 +39,30 @@@ extern char except_vec_nmi[]
>   	register_nmi_notifier(&fn##_nb);				\
>   })
>   
>  +asmlinkage void do_ade(struct pt_regs *regs);
>  +asmlinkage void do_be(struct pt_regs *regs);
>  +asmlinkage void do_ov(struct pt_regs *regs);
>  +asmlinkage void do_fpe(struct pt_regs *regs, unsigned long fcr31);
>  +asmlinkage void do_bp(struct pt_regs *regs);
>  +asmlinkage void do_tr(struct pt_regs *regs);
>  +asmlinkage void do_ri(struct pt_regs *regs);
>  +asmlinkage void do_cpu(struct pt_regs *regs);
>  +asmlinkage void do_msa_fpe(struct pt_regs *regs, unsigned int msacsr);
>  +asmlinkage void do_msa(struct pt_regs *regs);
>  +asmlinkage void do_mdmx(struct pt_regs *regs);
>  +asmlinkage void do_watch(struct pt_regs *regs);
>  +asmlinkage void do_mcheck(struct pt_regs *regs);
>  +asmlinkage void do_mt(struct pt_regs *regs);
>  +asmlinkage void do_dsp(struct pt_regs *regs);
>  +asmlinkage void do_reserved(struct pt_regs *regs);
>  +asmlinkage void do_ftlb(void);
>  +asmlinkage void do_gsexc(struct pt_regs *regs, u32 diag1);
>  +asmlinkage void do_daddi_ov(struct pt_regs *regs);
>  +
>  +asmlinkage void cache_parity_error(void);
>  +asmlinkage void ejtag_exception_handler(struct pt_regs *regs);
>  +asmlinkage void __noreturn nmi_exception_handler(struct pt_regs *regs);
> + asmlinkage void do_page_fault(struct pt_regs *regs,
> + 	unsigned long write, unsigned long address);
>   
>   #endif /* _ASM_TRAPS_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:[~2024-01-10 22:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-04 22:05 linux-next: manual merge of the asm-generic tree with the mm tree Stephen Rothwell
2024-01-10 22:22 ` Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-10-28 22:55 Stephen Rothwell
2024-11-21 23:56 ` Stephen Rothwell
2023-09-18  0:10 Stephen Rothwell
2023-09-18  1:28 ` Baoquan He
2023-11-02 21:34 ` 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=20240111092246.10ba37af@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=akpm@linux-foundation.org \
    --cc=arnd@arndb.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.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