From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Thomas Bogendoerfer <tsbogend@alpha•franken.de>,
Andrew Morton <akpm@linux-foundation•org>
Cc: Arnd Bergmann <arnd@arndb•de>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: linux-next: manual merge of the mips tree with the mm-nonmm-stable tree
Date: Tue, 2 Jan 2024 09:08:12 +1100 [thread overview]
Message-ID: <20240102090812.4243eb88@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1174 bytes --]
Hi all,
Today's linux-next merge of the mips tree got a conflict in:
arch/mips/kernel/traps.c
between commit:
ec47b986e53e ("mips: fix tlb_init() prototype")
from the mm-nonmm-stable tree and commit:
8e1803900ef1 ("MIPS: Remove unused shadow GPR support from vector irq setup")
from the mips 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/mips/kernel/traps.c
index c58c0c3c5b40,c1b2b18b0505..000000000000
--- a/arch/mips/kernel/traps.c
+++ b/arch/mips/kernel/traps.c
@@@ -2152,11 -2120,8 +2120,6 @@@ void *set_vi_handler(int n, vi_handler_
return (void *)old_handler;
}
- void *set_vi_handler(int n, vi_handler_t addr)
- {
- return set_vi_srs_handler(n, addr, 0);
- }
-extern void tlb_init(void);
--
/*
* Timer interrupt
*/
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
reply other threads:[~2024-01-01 22:08 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20240102090812.4243eb88@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=akpm@linux-foundation$(echo .)org \
--cc=arnd@arndb$(echo .)de \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=tsbogend@alpha$(echo .)franken.de \
/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