From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: Geert Uytterhoeven <geert@linux-m68k.org>,
Guenter Roeck <linux@roeck-us.net>
Cc: Sergey Shtylyov <s.shtylyov@omp.ru>,
Yoshinori Sato <ysato@users.sourceforge.jp>,
Rich Felker <dalias@libc.org>,
linux-sh@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] [RFT] sh: mach-r2d: Handle virq offset in cascaded IRL demux
Date: Mon, 10 Jul 2023 09:44:39 +0200 [thread overview]
Message-ID: <f27872c8f374a42fb7ea313314c47cdba2473b06.camel@physik.fu-berlin.de> (raw)
In-Reply-To: <CAMuHMdW=WDuqgXk_51T341vgXrcxYPO34ou=rKHZrZj8Yiw6Rw@mail.gmail.com>
Hi Geert!
On Mon, 2023-07-10 at 09:03 +0200, Geert Uytterhoeven wrote:
> Indeed, I hadn't tested that.
> My current tree isn't based on linux-next, but did have a build
> failure in the cdrom code, for which I had found your fix (thanks!) in
> linux-next...
So, there is a patch for this already? Is it going to be included for 6.5?
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer
`. `' Physicist
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
next prev parent reply other threads:[~2023-07-10 7:45 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-09 11:15 Geert Uytterhoeven
2023-07-09 11:52 ` John Paul Adrian Glaubitz
2023-07-09 11:53 ` John Paul Adrian Glaubitz
2023-07-09 11:58 ` John Paul Adrian Glaubitz
2023-07-09 12:50 ` Sergey Shtylyov
2023-07-09 13:51 ` Guenter Roeck
2023-07-10 1:13 ` Guenter Roeck
2023-07-10 7:03 ` Geert Uytterhoeven
2023-07-10 7:44 ` John Paul Adrian Glaubitz [this message]
2023-07-10 7:54 ` Geert Uytterhoeven
2023-07-10 7:57 ` John Paul Adrian Glaubitz
2023-07-10 8:18 ` Geert Uytterhoeven
2023-07-10 8:20 ` John Paul Adrian Glaubitz
2023-07-10 8:25 ` Geert Uytterhoeven
2023-07-10 7:23 ` John Paul Adrian Glaubitz
2023-07-13 6:54 ` John Paul Adrian Glaubitz
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=f27872c8f374a42fb7ea313314c47cdba2473b06.camel@physik.fu-berlin.de \
--to=glaubitz@physik.fu-berlin.de \
--cc=dalias@libc.org \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=s.shtylyov@omp.ru \
--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®