public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Max Filippov <jcmvbkbc@gmail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, Chris Zankel <chris@zankel.net>,
	Max Filippov <jcmvbkbc@gmail.com>
Subject: [PULL 00/16] Xtensa fixes for v6.6
Date: Thu, 28 Sep 2023 11:49:24 -0700	[thread overview]
Message-ID: <20230928184924.164748-1-jcmvbkbc@gmail.com> (raw)

Hi Linus,

please pull the following fixes for the Xtensa architecture.

The following changes since commit ce9ecca0238b140b88f43859b211c9fdfd8e5b70:

  Linux 6.6-rc2 (2023-09-17 14:40:24 -0700)

are available in the Git repository at:

  https://github.com/jcmvbkbc/linux-xtensa.git tags/xtensa-20230928

for you to fetch changes up to f54d02c8f2cc4b46ba2a3bd8252a6750453b6f2b:

  xtensa: boot/lib: fix function prototypes (2023-09-20 05:03:30 -0700)

----------------------------------------------------------------
Xtensa fixes for v6.6:

- fix build warnings from builds performed with W=1

----------------------------------------------------------------
Max Filippov (2):
      xtensa: add default definition for XCHAL_HAVE_DIV32
      xtensa: boot/lib: fix function prototypes

Randy Dunlap (14):
      xtensa: fault: include <asm/traps.h>
      xtensa: irq: include <asm/traps.h>
      xtensa: ptrace: add prototypes to <asm/ptrace.h>
      xtensa: processor.h: add init_arch() prototype
      xtensa: signal: include headers for function prototypes
      xtensa: stacktrace: include <asm/ftrace.h> for prototype
      xtensa: traps: add <linux/cpu.h> for function prototype
      irqchip: irq-xtensa-mx: include header for missing prototype
      xtensa: smp: add headers for missing function prototypes
      xtensa: hw_breakpoint: include header for missing prototype
      xtensa: tlb: include <asm/tlb.h> for missing prototype
      xtensa: iss/network: make functions static
      xtensa: boot: don't add include-dirs
      xtensa: umulsidi3: fix conditional expression

 arch/xtensa/boot/Makefile               | 3 +--
 arch/xtensa/boot/lib/zmem.c             | 5 +++--
 arch/xtensa/include/asm/core.h          | 4 ++++
 arch/xtensa/include/asm/hw_breakpoint.h | 1 +
 arch/xtensa/include/asm/processor.h     | 5 +++++
 arch/xtensa/include/asm/ptrace.h        | 3 +++
 arch/xtensa/include/asm/smp.h           | 1 +
 arch/xtensa/include/asm/tlb.h           | 2 ++
 arch/xtensa/kernel/hw_breakpoint.c      | 1 +
 arch/xtensa/kernel/irq.c                | 1 +
 arch/xtensa/kernel/ptrace.c             | 1 -
 arch/xtensa/kernel/signal.c             | 2 ++
 arch/xtensa/kernel/smp.c                | 1 +
 arch/xtensa/kernel/stacktrace.c         | 1 +
 arch/xtensa/kernel/traps.c              | 1 +
 arch/xtensa/lib/umulsidi3.S             | 4 +++-
 arch/xtensa/mm/fault.c                  | 1 +
 arch/xtensa/mm/tlb.c                    | 1 +
 arch/xtensa/platforms/iss/network.c     | 4 ++--
 drivers/irqchip/irq-xtensa-mx.c         | 1 +
 20 files changed, 35 insertions(+), 8 deletions(-)

-- 
Thanks.
-- Max

             reply	other threads:[~2023-09-28 18:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-28 18:49 Max Filippov [this message]
2023-09-29 16:29 ` [PULL 00/16] Xtensa fixes for v6.6 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=20230928184924.164748-1-jcmvbkbc@gmail.com \
    --to=jcmvbkbc@gmail.com \
    --cc=chris@zankel.net \
    --cc=linux-kernel@vger.kernel.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