The Linux Kernel Mailing List
 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 0/4] xtensa updates for v6.8
Date: Wed, 17 Jan 2024 03:29:33 -0800	[thread overview]
Message-ID: <20240117112933.303593-1-jcmvbkbc@gmail.com> (raw)

Hi Linus,

please pull the following updates for the Xtensa architecture.

The following changes since commit 2cc14f52aeb78ce3f29677c2de1f06c0e91471ab:

  Linux 6.7-rc3 (2023-11-26 19:59:33 -0800)

are available in the Git repository at:

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

for you to fetch changes up to a03cd7602a090eae277d2b79d43925661e7fbe9a:

  xtensa: don't produce FDPIC output with fdpic toolchain (2024-01-11 18:58:47 -0800)

----------------------------------------------------------------
Xtensa updates for v6.8

- small cleanups in the xtensa PCI and asmmacro code
- fix kernel build with FDPIC toolchain

----------------------------------------------------------------
Ilpo Järvinen (1):
      xtensa: Use PCI_HEADER_TYPE_MFD instead of literal

Masahiro Yamada (1):
      xtensa: replace <asm-generic/export.h> with <linux/export.h>

Max Filippov (1):
      xtensa: don't produce FDPIC output with fdpic toolchain

Yujie Liu (1):
      xtensa: fix variants path in the Kconfig help

 arch/xtensa/Kconfig                | 2 +-
 arch/xtensa/Makefile               | 6 +++++-
 arch/xtensa/include/asm/asmmacro.h | 2 +-
 arch/xtensa/lib/pci-auto.c         | 8 +++++---
 4 files changed, 12 insertions(+), 6 deletions(-)

-- 
Thanks.
-- Max

             reply	other threads:[~2024-01-17 11:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-17 11:29 Max Filippov [this message]
2024-01-17 20:03 ` [PULL 0/4] xtensa updates for v6.8 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=20240117112933.303593-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