From: Hans-Christian Egtvedt <egtvedt@samfundet.no>
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: Michal Marek <mmarek@suse.cz>,
"Yann E. MORIN" <yann.morin.1998@free.fr>,
linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org,
Haavard Skinnemoen <hskinnemoen@gmail.com>
Subject: Re: [PATCH 3/3] kconfig: Extend defconfig field size from 24 to 32
Date: Tue, 26 May 2015 13:52:11 +0200 [thread overview]
Message-ID: <20150526115211.GA18353@samfundet.no> (raw)
In-Reply-To: <1432640395-17310-3-git-send-email-geert+renesas@glider.be>
Around Tue 26 May 2015 13:39:55 +0200 or thereabout, Geert Uytterhoeven wrote:
> next-20150526 has 12 defconfigs with names longer than 24 characters,
> breaking alignment in "make help".
>
> The "winners" are "atngw100mkii_evklcd100_defconfig" and
> "atngw100mkii_evklcd101_defconfig", counting in at 32 characters.
>
> Extend the defconfig field size to 32 to restore alignment.
> Don't use a larger value, to not encourage people to create even longer
> defconfig names.
(-:
They were very explicit to the ordering code.
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
> Cc: Haavard Skinnemoen <hskinnemoen@gmail.com>
> Cc: Hans-Christian Egtvedt <egtvedt@samfundet.no>
Acked-by: Hans-Christian Egtvedt <egtvedt@samfundet.no>
> ---
> Makefile | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
<snipp diff>
--
mvh
Hans-Christian Egtvedt
prev parent reply other threads:[~2015-05-26 13:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-26 11:39 [PATCH 1/3] Blackfin: Wrap long "make help" text lines Geert Uytterhoeven
2015-05-26 11:39 ` [PATCH 2/3] kconfig: " Geert Uytterhoeven
2015-05-31 1:10 ` Diego Viola
2015-05-31 8:26 ` Geert Uytterhoeven
2015-05-31 12:53 ` Diego Viola
2015-05-31 18:14 ` Diego Viola
2015-06-04 14:43 ` Michal Marek
2015-05-26 11:39 ` [PATCH 3/3] kconfig: Extend defconfig field size from 24 to 32 Geert Uytterhoeven
2015-05-26 11:52 ` Hans-Christian Egtvedt [this message]
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=20150526115211.GA18353@samfundet.no \
--to=egtvedt@samfundet.no \
--cc=geert+renesas@glider.be \
--cc=hskinnemoen@gmail.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.cz \
--cc=yann.morin.1998@free.fr \
/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®