From: David Miller <davem@davemloft.net>
To: macro@orcam.me.uk
Cc: rdunlap@infradead.org, sam@ravnborg.org, schnelle@linux.ibm.com,
linux-kernel@vger.kernel.org, sudipm.mukherjee@gmail.com,
sparclinux@vger.kernel.org, linux-parport@lists.infradead.org
Subject: Re: [PATCH] parport_pc: don't allow driver for SPARC32
Date: Fri, 23 Jun 2023 16:33:29 +0100 (BST) [thread overview]
Message-ID: <20230623.163329.1458342120776268478.davem@davemloft.net> (raw)
In-Reply-To: <alpine.DEB.2.21.2306190202050.14084@angie.orcam.me.uk>
From: "Maciej W. Rozycki" <macro@orcam.me.uk>
Date: Mon, 19 Jun 2023 02:29:57 +0100 (BST)
> 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.
I'm good just too busy with networking and real life.
Thanks.
next prev parent reply other threads:[~2023-06-23 15:33 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
2023-06-23 15:33 ` David Miller [this message]
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=20230623.163329.1458342120776268478.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-parport@lists.infradead.org \
--cc=macro@orcam.me.uk \
--cc=rdunlap@infradead.org \
--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;
as well as URLs for NNTP newsgroup(s).