From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: "Dr. David Alan Gilbert" <linux@treblig.org>,
Sam Ravnborg <sam@ravnborg.org>
Cc: davem@davemloft.net, benh@kernel.crashing.org,
sparclinux@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] sparc: Use shared font data
Date: Tue, 25 Jul 2023 19:15:08 +0200 [thread overview]
Message-ID: <605d12e8a4fdcb238efc9b18fbd2637474de0049.camel@physik.fu-berlin.de> (raw)
In-Reply-To: <ZL/+Bz5C2Mxx0Msw@gallifrey>
Hi Dave!
On Tue, 2023-07-25 at 16:53 +0000, Dr. David Alan Gilbert wrote:
> * Sam Ravnborg (sam@ravnborg.org) wrote:
> > On Tue, Jul 25, 2023 at 12:58:51AM +0100, linux@treblig.org wrote:
> > > From: "Dr. David Alan Gilbert" <linux@treblig.org>
> > >
> > > sparc has a 'btext' font used for the console which is almost identical
> > > to the shared font_sun8x16, so use it rather than duplicating the data.
> > >
> > > They were actually identical until about a decade ago when
> > > commit bcfbeecea11c ("drivers: console: font_: Change a glyph from
> > > "broken bar" to "vertical line"")
> > >
> > > which changed the | in the shared font to be a solid
> > > bar rather than a broken bar. That's the only difference.
> > >
> > > This was originally spotted by PMD which noticed that PPC does
> > > the same thing with the same data, and they also share a bunch
> > > of functions to manipulate the data. The PPC code and the functions
> > > I'll look at another time if this patch is OK.
> > >
> > > Tested very lightly with a boot without FS in qemu.
> > >
> > > Signed-off-by: Dr. David Alan Gilbert <linux@treblig.org>
> >
> > Looks good, thanks for the fixes.
> > Reviewed-by: Sam Ravnborg <sam@ravnborg.org>
>
> Thanks
>
> > Let's hope someone picks it up...
>
> I was hoping Dave would, but I realise Sparc doesn't get much
> these days.
> Of course if anyone feels guilty about their own patches adding code
> they can take this patch to make ~340 lines of penance.
You can ask Andrew Morton to pick it up through his tree. He usually does
that when no one else is willing to pick a patch up.
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer
`. `' Physicist
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
next prev parent reply other threads:[~2023-07-25 17:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-24 23:58 linux
2023-07-25 16:10 ` Sam Ravnborg
2023-07-25 16:53 ` Dr. David Alan Gilbert
2023-07-25 17:15 ` John Paul Adrian Glaubitz [this message]
2023-07-25 23:09 ` 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=605d12e8a4fdcb238efc9b18fbd2637474de0049.camel@physik.fu-berlin.de \
--to=glaubitz@physik.fu-berlin.de \
--cc=benh@kernel.crashing.org \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@treblig.org \
--cc=sam@ravnborg.org \
--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
all inboxes | Powered by JetHome®