From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Takashi Iwai <tiwai@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH RFC 0/3] Automatically choose a bigger font for high resolution screens
Date: Thu, 20 Jun 2019 08:28:21 +0200 [thread overview]
Message-ID: <20190620062821.GA20578@kroah.com> (raw)
In-Reply-To: <20190618203425.10723-1-tiwai@suse.de>
On Tue, Jun 18, 2019 at 10:34:22PM +0200, Takashi Iwai wrote:
> Hi,
>
> this is an RFC patch for automatically selecting a bigger font for
> high resolution monitors if available. Although we recently got a
> 16x32 sized font support in the kernel, using it still requires some
> extra kernel option. This patch reduces this and the kernel will pick
> up a bigger font.
>
> The logic is simply checking the text screen size. If it's over a
> threshold, the penalty is given to the function that chooses the
> default font.
>
> The threshold was chosen so that the normal display up to Full HD
> won't be affected.
>
> There are two preliminary patches and they are merely cleanups. They
> can be applied no matter whether to take the last patch or not.
I applied the first two patches, as they seem sane.
I like the idea of the last one, and have no objections to it. I can
apply it too if you want and we can see what happens :)
thanks,
greg k-h
next prev parent reply other threads:[~2019-06-20 6:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-18 20:34 [PATCH RFC 0/3] Automatically choose a bigger font for high resolution screens Takashi Iwai
2019-06-18 20:34 ` [PATCH RFC 1/3] fonts: Fix coding style Takashi Iwai
2019-06-18 20:34 ` [PATCH RFC 2/3] fonts: Use BUILD_BUG_ON() for checking empty font table Takashi Iwai
2019-06-18 23:05 ` Randy Dunlap
2019-06-19 5:36 ` Takashi Iwai
2019-06-18 20:34 ` [PATCH RFC 3/3] fonts: Prefer a bigger font for high resolution screens Takashi Iwai
2019-06-20 6:28 ` Greg Kroah-Hartman [this message]
2019-06-20 7:43 ` [PATCH RFC 0/3] Automatically choose " Takashi Iwai
2019-06-20 8:12 ` Greg Kroah-Hartman
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=20190620062821.GA20578@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tiwai@suse.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.