mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
	Artur Rojek <contact@artur-rojek.eu>,
	Rich Felker <dalias@libc.org>,
	Yoshinori Sato <ysato@users.sourceforge.jp>,
	linux-sh@vger.kernel.org,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] sh fixes for v6.5 - Correction
Date: Thu, 13 Jul 2023 10:53:20 +0200	[thread overview]
Message-ID: <59bbb42c51b5c9eaa6afb8208f2a2c937a39f1c0.camel@physik.fu-berlin.de> (raw)
In-Reply-To: <90e6042f3a82d5e9b4cf475603dcb73ca5e821d8.camel@physik.fu-berlin.de>

Hi Linus!

On Thu, 2023-07-13 at 09:25 +0200, John Paul Adrian Glaubitz wrote:
> Hi Linus!
> 
> The sh updates for v6.5 introduced multiple regressions that this pull request addresses.
> In particular, the change a8ac2961148e ("sh: Avoid using IRQ0 on SH3 and SH4") causes
> several boards to hang during boot due to incorrect IRQ numbers.
> 
> Geert Uytterhoeven has contributed patches that handle the virq offset in the IRQ code
> for the dreamcast, highlander and r2d boards while Artur Rojek has contributed a patch
> which handles the virq offset for the hd64461 companion chip.
> 
> With the series applied, the affected boards will boot the kernel again without issues.

Apparently, booting on dreamcast currently does not work even with the patches applied due
to unreleated issues. So, please drop the last paragraph from the pull message to avoid
confusion.

Thanks,
Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer
`. `'   Physicist
  `-    GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

  reply	other threads:[~2023-07-13  8:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-13  7:25 [GIT PULL] sh fixes for v6.5 John Paul Adrian Glaubitz
2023-07-13  8:53 ` John Paul Adrian Glaubitz [this message]
2023-07-13 21:41 ` 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=59bbb42c51b5c9eaa6afb8208f2a2c937a39f1c0.camel@physik.fu-berlin.de \
    --to=glaubitz@physik.fu-berlin.de \
    --cc=contact@artur-rojek.eu \
    --cc=dalias@libc.org \
    --cc=geert@linux-m68k.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=ysato@users.sourceforge.jp \
    /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

all inboxes | Powered by JetHome®