From: Wang YanQing <udknight@gmail.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: jslaby@suse.cz, airlied@redhat.com, akpm@linux-foundation.org,
kilobyte@angband.pl, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fonts:Kconfig: fix default enable FONT_8x8 and FONT_8x16 at the same time
Date: Mon, 30 Dec 2013 14:48:42 +0800 [thread overview]
Message-ID: <20131230064842.GA6592@udknight> (raw)
In-Reply-To: <20131230053430.GA11990@kroah.com>
On Sun, Dec 29, 2013 at 09:34:30PM -0800, Greg KH wrote:
> On Mon, Dec 30, 2013 at 11:37:45AM +0800, Wang YanQing wrote:
> > FONT_8x8 and FONT_8x16 have the same default value line:
> > "default y if !SPARC && !FONTS"
> >
> > I test run "make defconfig" for x86 will enable FONT_8x8 and FONT_8x16 at
> > the same time.
> >
> > This patch fix it, because FONT_AUTOSELECT choice FONT_8x16, so
> > I decide to disable FONT_8x8, this patch will reduce size of kernel.
> >
> > Signed-off-by: Wang YanQing <udknight@gmail.com>
> > ---
> > lib/fonts/Kconfig | 1 -
> > 1 file changed, 1 deletion(-)
>
> I am not the maintainer of this file, sorry. Also, I don't think it's
> correct, if you want, you can always disable this option on your own.
>
Hi Greg KH.
Sorry for confusion, the default behavior enable FONT_8x8 and FONT_8x16,
FONT_8x8 eat ~50KB memory, but kernel never use it. I think this is not
good default behavior.
Thanks.
next prev parent reply other threads:[~2013-12-30 6:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-30 3:37 [PATCH] fonts:Kconfig: fix default enable FONT_8x8 and FONT_8x16 at the same time Wang YanQing
2013-12-30 5:34 ` Greg KH
2013-12-30 6:48 ` Wang YanQing [this message]
2013-12-30 18:21 ` Randy Dunlap
-- strict thread matches above, loose matches on Subject: below --
2013-12-30 6:53 Wang YanQing
2013-12-30 8:51 ` Geert Uytterhoeven
2013-12-31 1:19 ` Wang YanQing
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=20131230064842.GA6592@udknight \
--to=udknight@gmail.com \
--cc=airlied@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.cz \
--cc=kilobyte@angband.pl \
--cc=linux-kernel@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 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.