From: Finn Thain <fthain@linux-m68k.org>
To: Christophe Leroy <christophe.leroy@csgroup.eu>
Cc: Stan Johnson <userm57@yahoo.com>,
"Dr. David Alan Gilbert" <linux@treblig.org>,
mpe@ellerman.id.au, npiggin@gmail.com, sam@ravnborg.org,
benh@kernel.crashing.org, linuxppc-dev@lists.ozlabs.org,
linux-kernel@vger.kernel.org, rdunlap@infradead.org,
Cedar Maxwell <cedarmaxwell@mac.com>,
"maddy@linux.ibm.com" <maddy@linux.ibm.com>
Subject: Re: [PATCH v4] powerpc: Use shared font data
Date: Thu, 6 Nov 2025 22:50:27 +1100 (AEDT) [thread overview]
Message-ID: <b4737133-a33c-f4d1-cc4b-0c0b70c45635@linux-m68k.org> (raw)
In-Reply-To: <994bea8c-7b28-4aae-a6b3-e4f33731cb29@csgroup.eu>
[-- Attachment #1: Type: text/plain, Size: 625 bytes --]
On Thu, 6 Nov 2025, Christophe Leroy wrote:
> Le 06/11/2025 à 05:11, Finn Thain a écrit :
> >
> > On Wed, 5 Nov 2025, Christophe Leroy wrote:
> >
> >> 1/ Either build font_sun8x16.o with -fPIC
> >> ...
> >>
> >> 2/ Or add a PTRRELOC:
> >> ...
> >
> > Thanks for your help with this, Christophe.
> >
> > I fixed up the whitespace problems and forwarded those patches to Stan,
> > along with instructions for applying them. He tells me that patch 2 fixed
> > the hang. Patch 1 did not.
>
> Fine. Then let's use PTRRELOC.
>
> Will you or David submit the patch ?
>
OK, I'll submit the patch.
next prev parent reply other threads:[~2025-11-06 11:51 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-25 14:27 [PATCH v4] powerpc: Use shared font data linux
2023-09-30 13:15 ` Dr. David Alan Gilbert
2023-10-01 12:08 ` Michael Ellerman
2023-10-02 12:21 ` Dr. David Alan Gilbert
2023-10-15 10:04 ` Michael Ellerman
2025-11-02 5:02 ` Stan Johnson
2025-11-02 11:20 ` Finn Thain
2025-11-02 17:09 ` Dr. David Alan Gilbert
2025-11-02 19:01 ` Stan Johnson
2025-11-03 1:33 ` Finn Thain
2025-11-03 1:48 ` Dr. David Alan Gilbert
2025-11-03 7:26 ` Finn Thain
2025-11-04 17:59 ` Dr. David Alan Gilbert
2025-11-04 19:49 ` Stan Johnson
2025-11-04 21:59 ` Dr. David Alan Gilbert
2025-11-05 4:13 ` QEMU limitations, was " Finn Thain
2025-11-05 14:58 ` Dr. David Alan Gilbert
2025-11-05 21:44 ` Christophe Leroy
2025-11-05 23:48 ` Finn Thain
2025-11-06 4:11 ` Finn Thain
2025-11-06 9:28 ` Christophe Leroy
2025-11-06 11:50 ` Finn Thain [this message]
2025-11-06 12:07 ` Dr. David Alan Gilbert
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=b4737133-a33c-f4d1-cc4b-0c0b70c45635@linux-m68k.org \
--to=fthain@linux-m68k.org \
--cc=benh@kernel.crashing.org \
--cc=cedarmaxwell@mac.com \
--cc=christophe.leroy@csgroup.eu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@treblig.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@linux.ibm.com \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.com \
--cc=rdunlap@infradead.org \
--cc=sam@ravnborg.org \
--cc=userm57@yahoo.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).