From: thomas.petazzoni@free-electrons.com (Thomas Petazzoni)
To: linux-snps-arc@lists.infradead.org
Subject: [uclibc-ng-devel] [PATCH] ARC: Enable getpt() support in ARC defconfigs
Date: Wed, 1 Mar 2017 21:25:33 +0100 [thread overview]
Message-ID: <20170301212533.6ddcfc0f@free-electrons.com> (raw)
In-Reply-To: <1488392734.4659.54.camel@synopsys.com>
Hello,
On Wed, 1 Mar 2017 18:25:35 +0000, Alexey Brodkin wrote:
> That means for building of our toolchain we'll need to have
> separately stored "defconfigs" in some form. Let's see what Anton says on that :)
>
> And regardless of what mr Anton says having off-the-tree defconfigs is not the best idea
> because with time options will go in and out and occasionally we'll have outdated
> defconfigs.
What would they be off-tree?
What I meant is that when you look at the per architecture defconfigs,
they are also all exactly the same, except for the TARGET_<foo> option.
So instead of having this big duplication, my suggestion is to get rid
of architecture-specific defconfig, and just have a few
architecture-independent defconfig, addressing common use cases (such
as "minimal" and "feature full").
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-03-01 20:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-28 19:02 [PATCH] ARC: Enable getpt() support in ARC defconfigs Vlad Zakharov
2017-03-01 15:24 ` [uclibc-ng-devel] " Thomas Petazzoni
2017-03-01 18:00 ` Vineet Gupta
2017-03-01 18:25 ` Alexey Brodkin
2017-03-01 18:35 ` Vineet Gupta
2017-03-01 18:57 ` Anton Kolesov
2017-03-01 19:10 ` Vineet Gupta
2017-03-01 19:28 ` Waldemar Brodkorb
2017-03-01 20:25 ` Thomas Petazzoni [this message]
2017-03-01 21:30 ` Alexey Brodkin
2017-03-01 21:45 ` Thomas Petazzoni
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=20170301212533.6ddcfc0f@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=linux-snps-arc@lists.infradead.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.