[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.21.2306190202050.14084@angie.orcam.me.uk>
Date: Mon, 19 Jun 2023 02:29:57 +0100 (BST)
From: "Maciej W. Rozycki" <macro@...am.me.uk>
To: Randy Dunlap <rdunlap@...radead.org>
cc: Sam Ravnborg <sam@...nborg.org>,
Niklas Schnelle <schnelle@...ux.ibm.com>,
linux-kernel@...r.kernel.org,
Sudip Mukherjee <sudipm.mukherjee@...il.com>,
"David S. Miller" <davem@...emloft.net>,
sparclinux@...r.kernel.org, linux-parport@...ts.infradead.org
Subject: Re: [PATCH] parport_pc: don't allow driver for SPARC32
Hi Randy,
> > What happened to DaveM?
>
> I haven't seen him merge any arch/sparc/ patches lately.
> I have a couple that are still pending.
Oh, I hope he's been doing good then, and it's just a change of life
priorities or suchlike. Patch reviews can take a lot of mental effort,
and I can't claim I've been as effective as I wished to with stuff that
lands on my plate either.
> > In any case after a couple of iterations I have made a succesful build of
> > a 32-bit SPARC toolchain now, which I was able to verify a fix with I have
>
> Is your newly built toolchain for riscv hosting?
Are you asking whether the SPARC toolchain has been built/installed on a
RISC-V system? If so, then no, it hasn't. It runs on POWER9.
Maciej
Powered by blists - more mailing lists