mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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 17:23:21 -0700	[thread overview]
Message-ID: <ea8b0e25-fd2e-4fe1-3157-7556e29eee87@infradead.org> (raw)
In-Reply-To: <alpine.DEB.2.21.2306190000530.14084@angie.orcam.me.uk>

Hi,

On 6/18/23 16:42, Maciej W. Rozycki wrote:
> On Fri, 7 Apr 2023, Randy Dunlap wrote:
> 
>> /me wishes that we had a Sparc maintainer.
> 
>  What happened to DaveM?

I haven't seen him merge any arch/sparc/ patches lately.
I have a couple that are still pending.

>  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?

> outlined earlier in this thread.  Posted as archived at: 
> <https://lore.kernel.org/r/alpine.DEB.2.21.2306182347101.14084@angie.orcam.me.uk/>.

thanks.
-- 
~Randy

  reply	other threads:[~2023-06-19  0:23 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-06 16:05 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 [this message]
2023-06-19  1:29                 ` Maciej W. Rozycki
2023-06-19  2:35                   ` Randy Dunlap
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=ea8b0e25-fd2e-4fe1-3157-7556e29eee87@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 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®