From: Randy Dunlap <rdunlap@infradead.org>
To: "Maciej W. Rozycki" <macro@orcam.me.uk>
Cc: Sam Ravnborg <sam@ravnborg.org>,
Niklas Schnelle <schnelle@linux.ibm.com>,
linux-kernel@vger.kernel.org,
Sudip Mukherjee <sudipm.mukherjee@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
sparclinux@vger.kernel.org, linux-parport@lists.infradead.org
Subject: Re: [PATCH] parport_pc: don't allow driver for SPARC32
Date: Sun, 18 Jun 2023 19:35:17 -0700 [thread overview]
Message-ID: <0b59e7f8-542a-dc2d-08bd-8b42e03e32aa@infradead.org> (raw)
In-Reply-To: <alpine.DEB.2.21.2306190202050.14084@angie.orcam.me.uk>
On 6/18/23 18:29, Maciej W. Rozycki wrote:
> 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.
Yes, that's what I was asking.
So you could have used the compilers that Arnd builds:
https://mirrors.edge.kernel.org/pub/tools/crosstool/
Thanks.
--
~Randy
next prev parent reply other threads:[~2023-06-19 2:35 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-06 16:05 [PATCH] parport_pc: don't allow driver for SPARC32 Randy Dunlap
2023-04-06 19:28 ` Sam Ravnborg
2023-04-06 19:49 ` Maciej W. Rozycki
2023-04-06 19:51 ` Randy Dunlap
2023-04-06 20:32 ` Sam Ravnborg
2023-04-06 21:01 ` Maciej W. Rozycki
2023-04-06 21:31 ` Randy Dunlap
2023-04-07 20:03 ` Sam Ravnborg
2023-04-07 21:01 ` Maciej W. Rozycki
2023-04-07 21:10 ` Randy Dunlap
2023-06-18 23:42 ` Maciej W. Rozycki
2023-06-19 0:23 ` Randy Dunlap
2023-06-19 1:29 ` Maciej W. Rozycki
2023-06-19 2:35 ` Randy Dunlap [this message]
2023-06-23 15:33 ` David Miller
2023-06-23 17:22 ` Sam Ravnborg
2023-06-23 19:20 ` Randy Dunlap
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=0b59e7f8-542a-dc2d-08bd-8b42e03e32aa@infradead.org \
--to=rdunlap@infradead.org \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-parport@lists.infradead.org \
--cc=macro@orcam.me.uk \
--cc=sam@ravnborg.org \
--cc=schnelle@linux.ibm.com \
--cc=sparclinux@vger.kernel.org \
--cc=sudipm.mukherjee@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.