From: Randy Dunlap <rdunlap@infradead.org>
To: sparclinux <sparclinux@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Andreas Larsson <andreas@gaisler.com>
Cc: "Maciej W. Rozycki" <macro@orcam.me.uk>
Subject: sparc: patch to fix parport_pc build on 32-bit
Date: Thu, 22 Feb 2024 21:15:28 -0800 [thread overview]
Message-ID: <4c4e2845-c7a8-4d0b-aa4a-7c5e3399b3dc@infradead.org> (raw)
Hi Andreas,
Please pick up this patch from June/2023. I have already replied to
the patch with:
Acked-by: Randy Dunlap <rdunlap@infradead.org>
Tested-by: Randy Dunlap <rdunlap@infradead.org> # build-tested
and I just rechecked it on linux-next-20240223 to make sure that it
builds cleanly. It does; however, there is one trivial merge warning:
patching file arch/sparc/include/asm/parport.h
Hunk #1 succeeded at 20 (offset 1 line).
Hunk #2 succeeded at 252 (offset 1 line).
The patch:
https://lore.kernel.org/lkml/alpine.DEB.2.21.2306190121540.14084@angie.orcam.me.uk/
Thank you.
--
#Randy
next reply other threads:[~2024-02-23 5:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-23 5:15 Randy Dunlap [this message]
2024-02-23 9:34 ` sparc: patch to fix parport_pc build on 32-bit Sam Ravnborg
2024-02-23 19:39 ` Sam Ravnborg
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=4c4e2845-c7a8-4d0b-aa4a-7c5e3399b3dc@infradead.org \
--to=rdunlap@infradead.org \
--cc=andreas@gaisler.com \
--cc=linux-kernel@vger.kernel.org \
--cc=macro@orcam.me.uk \
--cc=sparclinux@vger.kernel.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).