linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Greg Ungerer <gerg@linux-m68k.org>,
	Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Michael Schmitz <schmitzmic@gmail.com>
Subject: linux-next: manual merge of the m68knommu tree with the m68k tree
Date: Tue, 10 May 2022 09:44:42 +1000	[thread overview]
Message-ID: <20220510094442.26826532@canb.auug.org.au> (raw)

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

Hi all,

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

  arch/m68k/kernel/ptrace.c

between commit:

  c862fe70b023 ("m68k: Wire up syscall_trace_enter/leave for m68k")

from the m68k tree and commit:

  0d91043d8bdf ("m68knommu: implement minimal regset support")

from the m68knommu 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/m68k/kernel/ptrace.c
index daebccdd2c09,4349b9c4dd68..000000000000
--- a/arch/m68k/kernel/ptrace.c
+++ b/arch/m68k/kernel/ptrace.c
@@@ -284,3 -292,60 +286,59 @@@ asmlinkage void syscall_trace_leave(voi
  	if (test_thread_flag(TIF_SYSCALL_TRACE))
  		ptrace_report_syscall_exit(task_pt_regs(current), 0);
  }
 -#endif /* CONFIG_COLDFIRE */
+ 
+ #if defined(CONFIG_BINFMT_ELF_FDPIC) && defined(CONFIG_ELF_CORE)
+ /*
+  * Currently the only thing that needs to use regsets for m68k is the
+  * coredump support of the elf_fdpic loader. Implement the minimum
+  * definitions required for that.
+  */
+ static int m68k_regset_get(struct task_struct *target,
+ 			   const struct user_regset *regset,
+ 			   struct membuf to)
+ {
+ 	struct pt_regs *ptregs = task_pt_regs(target);
+ 	u32 uregs[ELF_NGREG];
+ 
+ 	ELF_CORE_COPY_REGS(uregs, ptregs);
+ 	return membuf_write(&to, uregs, sizeof(uregs));
+ }
+ 
+ enum m68k_regset {
+ 	REGSET_GPR,
+ #ifdef CONFIG_FPU
+ 	REGSET_FPU,
+ #endif
+ };
+ 
+ static const struct user_regset m68k_user_regsets[] = {
+ 	[REGSET_GPR] = {
+ 		.core_note_type = NT_PRSTATUS,
+ 		.n = ELF_NGREG,
+ 		.size = sizeof(u32),
+ 		.align = sizeof(u16),
+ 		.regset_get = m68k_regset_get,
+ 	},
+ #ifdef CONFIG_FPU
+ 	[REGSET_FPU] = {
+ 		.core_note_type = NT_PRFPREG,
+ 		.n = sizeof(struct user_m68kfp_struct) / sizeof(u32),
+ 		.size = sizeof(u32),
+ 		.align = sizeof(u32),
+ 	}
+ #endif /* CONFIG_FPU */
+ };
+ 
+ static const struct user_regset_view user_m68k_view = {
+ 	.name = "m68k",
+ 	.e_machine = EM_68K,
+ 	.ei_osabi = ELF_OSABI,
+ 	.regsets = m68k_user_regsets,
+ 	.n = ARRAY_SIZE(m68k_user_regsets)
+ };
+ 
+ const struct user_regset_view *task_user_regset_view(struct task_struct *task)
+ {
+ 	return &user_m68k_view;
+ }
+ #endif /* CONFIG_BINFMT_ELF_FDPIC && CONFIG_ELF_CORE */

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

             reply	other threads:[~2022-05-09 23:45 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-09 23:44 Stephen Rothwell [this message]
2022-05-10  3:37 ` linux-next: manual merge of the m68knommu tree with the m68k tree Michael Schmitz
2022-05-10  4:15   ` Greg Ungerer
  -- strict thread matches above, loose matches on Subject: below --
2020-09-09 23:34 Stephen Rothwell
2020-10-13  7:24 ` Stephen Rothwell
2019-07-01 23:09 Stephen Rothwell
2019-07-09  0:25 ` Stephen Rothwell
2011-11-14  0:03 Stephen Rothwell
2011-11-14  0:29 ` Greg Ungerer
2011-11-09  0:15 Stephen Rothwell
2011-11-09  7:08 ` Greg Ungerer
2011-11-09  7:13   ` Geert Uytterhoeven
2011-11-09  7:37     ` Greg Ungerer
2011-11-09  8:19       ` Geert Uytterhoeven
2011-11-09  0:15 Stephen Rothwell
2011-06-22  1:12 Stephen Rothwell
2011-06-22  6:34 ` Greg Ungerer
2011-06-22  8:29   ` Geert Uytterhoeven
2011-06-23  6:12     ` Greg Ungerer
2010-09-14  0:51 Stephen Rothwell
2010-09-14  1:21 ` Greg Ungerer
2010-09-14  8:47   ` Geert Uytterhoeven
2009-11-26  0:58 Stephen Rothwell
2009-11-26 21:29 ` Geert Uytterhoeven
2009-11-27  4:43   ` Greg Ungerer
2009-11-27  8:43     ` Geert Uytterhoeven
2009-11-27 11:23       ` Greg Ungerer
2009-11-27 21:21         ` Geert Uytterhoeven

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=20220510094442.26826532@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=geert@linux-m68k.org \
    --cc=gerg@linux-m68k.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=schmitzmic@gmail.com \
    /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;
as well as URLs for NNTP newsgroup(s).