public inbox for linux-m68k@lists.linux-m68k.org
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Greg Ungerer <gerg@linux-m68k.org>,
	linux-m68k@lists.linux-m68k.org, linux-kernel@vger.kernel.org,
	Geert Uytterhoeven <geert@linux-m68k.org>
Subject: [GIT PULL] m68k updates for v6.3
Date: Mon, 20 Feb 2023 13:41:09 +0100	[thread overview]
Message-ID: <20230220124109.679256-1-geert@linux-m68k.org> (raw)

	Hi Linus,

The following changes since commit 1b929c02afd37871d5afb9d498426f83432e71c2:

  Linux 6.2-rc1 (2022-12-25 13:41:39 -0800)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/geert/linux-m68k.git tags/m68k-for-v6.3-tag1

for you to fetch changes up to 1e5b5df65af99013b4d31607ddb3ca5731dbe44d:

  m68k: /proc/hardware should depend on PROC_FS (2023-02-13 11:34:49 +0100)

----------------------------------------------------------------
m68k updates for v6.3

  - Add seccomp support,
  - Defconfig updates,
  - Miscellaneous fixes and improvements.

Thanks for pulling!

----------------------------------------------------------------
Geert Uytterhoeven (1):
      m68k: defconfig: Update defconfigs for v6.2-rc3

Michael Schmitz (3):
      m68k: Check syscall_trace_enter() return code
      m68k: Add kernel seccomp support
      selftests/seccomp: Add m68k support

Randy Dunlap (1):
      m68k: /proc/hardware should depend on PROC_FS

Xin Gao (1):
      m68k: q40: Do not initialise statics to 0

 .../seccomp/seccomp-filter/arch-support.txt        |  2 +-
 arch/m68k/68000/entry.S                            |  2 +
 arch/m68k/Kconfig                                  |  2 +
 arch/m68k/Kconfig.devices                          |  1 +
 arch/m68k/coldfire/entry.S                         |  2 +
 arch/m68k/configs/amiga_defconfig                  |  3 --
 arch/m68k/configs/apollo_defconfig                 |  3 --
 arch/m68k/configs/atari_defconfig                  |  3 --
 arch/m68k/configs/bvme6000_defconfig               |  3 --
 arch/m68k/configs/hp300_defconfig                  |  3 --
 arch/m68k/configs/mac_defconfig                    |  3 --
 arch/m68k/configs/multi_defconfig                  |  4 +-
 arch/m68k/configs/mvme147_defconfig                |  3 --
 arch/m68k/configs/mvme16x_defconfig                |  3 --
 arch/m68k/configs/q40_defconfig                    |  3 --
 arch/m68k/configs/sun3_defconfig                   |  3 --
 arch/m68k/configs/sun3x_defconfig                  |  3 --
 arch/m68k/include/asm/seccomp.h                    | 11 +++++
 arch/m68k/include/asm/syscall.h                    | 57 ++++++++++++++++++++++
 arch/m68k/include/asm/thread_info.h                |  2 +
 arch/m68k/kernel/entry.S                           |  6 +++
 arch/m68k/kernel/ptrace.c                          |  6 ++-
 arch/m68k/q40/q40ints.c                            |  4 +-
 tools/testing/selftests/seccomp/seccomp_bpf.c      |  8 ++-
 24 files changed, 99 insertions(+), 41 deletions(-)
 create mode 100644 arch/m68k/include/asm/seccomp.h

Gr{oetje,eeting}s,

						Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
							    -- Linus Torvalds

             reply	other threads:[~2023-02-20 12:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-20 12:41 Geert Uytterhoeven [this message]
2023-02-21 23:40 ` [GIT PULL] m68k updates for v6.3 pr-tracker-bot

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=20230220124109.679256-1-geert@linux-m68k.org \
    --to=geert@linux-m68k.org \
    --cc=akpm@linux-foundation.org \
    --cc=gerg@linux-m68k.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-m68k@lists.linux-m68k.org \
    --cc=torvalds@linux-foundation.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