public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Helge Deller <deller@gmx.de>
To: Linus Torvalds <torvalds@linux-foundation.org>,
	linux-kernel@vger.kernel.org, linux-parisc@vger.kernel.org,
	James Bottomley <James.Bottomley@hansenpartnership.com>,
	John David Anglin <dave.anglin@bell.net>
Subject: [GIT PULL] parisc architecture fixes for v6.1-rc4
Date: Wed, 2 Nov 2022 17:26:13 +0100	[thread overview]
Message-ID: <Y2KaFoe7n4lkr25c@p100> (raw)

Hi Linus,

please pull some fixes for the parisc architecture for 6.1-rc4.

This patchset handles mostly oddities with the serial port 8250_gsc.c driver.
Although the name suggests it's just for serial ports on the GSC bus (e.g. in
older PA-RISC machines), it handles serial ports on PA-RISC PCI devices (e.g.
on the SuperIO chip) as well.
Thus this patchset renames the driver to 8250_parisc and fixes the config
dependencies.
The other change is a cleanup on how the device IDs of devices in a PA-RISC
machine are shown at startup.

Thanks,
Helge

-----

The following changes since commit 9abf2313adc1ca1b6180c508c25f22f9395cc780:

  Linux 6.1-rc1 (2022-10-16 15:36:24 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/deller/parisc-linux.git tags/parisc-for-6.1-2

for you to fetch changes up to 2b6ae0962b421103feb41a80406732944b0665b3:

  parisc: Avoid printing the hardware path twice (2022-10-31 15:37:14 +0100)

----------------------------------------------------------------
parisc architecture fixes for kernel v6.1-rc4:

Rename the serial port 8250_gsc.c driver to 8250_parisc.c and cleanup
how the device IDs of devices in a PA-RISC machine are shown at startup.

----------------------------------------------------------------
Helge Deller (5):
      parisc: Make 8250_gsc driver dependend on CONFIG_PARISC
      parisc/serial: Rename 8250_gsc.c to 8250_parisc.c
      parisc: Use signed char for hardware path in pdc.h
      parisc: Export iosapic_serial_irq() symbol for serial port driver
      parisc: Avoid printing the hardware path twice

Lukas Bulwahn (1):
      MAINTAINERS: adjust entry after renaming parisc serial driver

 MAINTAINERS                                        |  2 +-
 arch/parisc/include/asm/hardware.h                 | 12 ++++----
 arch/parisc/include/uapi/asm/pdc.h                 | 36 ++++++++--------------
 arch/parisc/kernel/drivers.c                       | 14 ++++-----
 drivers/parisc/iosapic.c                           |  1 +
 drivers/parisc/pdc_stable.c                        | 34 ++++++++++----------
 .../tty/serial/8250/{8250_gsc.c => 8250_parisc.c}  |  0
 drivers/tty/serial/8250/Kconfig                    |  4 +--
 drivers/tty/serial/8250/Makefile                   |  2 +-
 9 files changed, 47 insertions(+), 58 deletions(-)
 rename drivers/tty/serial/8250/{8250_gsc.c => 8250_parisc.c} (100%)

             reply	other threads:[~2022-11-02 16:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-02 16:26 Helge Deller [this message]
2022-11-02 18:38 ` [GIT PULL] parisc architecture fixes for v6.1-rc4 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=Y2KaFoe7n4lkr25c@p100 \
    --to=deller@gmx.de \
    --cc=James.Bottomley@hansenpartnership.com \
    --cc=dave.anglin@bell.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-parisc@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