From: Scott Wood <scottwood@freescale.com>
To: Timur Tabi <timur@codeaurora.org>
Cc: "linuxppc-dev@ozlabs.org" <linuxppc-dev@ozlabs.org>,
Richard Schmitt <richard.schmitt@freescale.com>,
Lijun Pan <Lijun.Pan@freescale.com>
Subject: Re: new way of writing defconfigs for freescale's powerpc platforms
Date: Mon, 20 Apr 2015 21:09:12 -0500 [thread overview]
Message-ID: <1429582152.4352.73.camel@freescale.com> (raw)
In-Reply-To: <CAOZdJXWnh3PbZ8FRFzJ9=h+bFF3_Uqeu=hzoqD6GYF8acQ21kQ@mail.gmail.com>
On Mon, 2015-04-20 at 21:02 -0500, Timur Tabi wrote:
> On Mon, Apr 20, 2015 at 3:31 PM, Scott Wood <scottwood@freescale.com> wrote:
> >
> >
> > The ability to merge configs is already there. We're just talking about
> > using that functionality.
>
> Why do you need a powerpc-specific way to use merge_config.sh? Other
> architectures have the same problem with defconfigs.
What are you perceiving as "powerpc-specific" about what we're
proposing? Are you complaining about the actual content of which
fragments to use to produce which defconfigs going in arch/powerpc?
> Besides, wouldn't it make more sense to define a new defconfig type,
> like p1_defconfig.merge, and if you do "make p1_defconfig.merge" it
> knows to call merge_config.sh?
That's already there. "make <foo>.config".
-Scott
next prev parent reply other threads:[~2015-04-21 2:09 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-09 21:52 new way of writing defconfigs for freescale's powerpc platforms Lijun Pan
2015-04-09 22:31 ` Scott Wood
2015-04-16 4:44 ` Bob Cochran
2015-04-16 13:20 ` Bob Cochran
2015-04-16 13:37 ` Richard Schmitt
2015-04-16 18:39 ` Scott Wood
2015-04-16 17:04 ` Lijun Pan
2015-04-17 0:54 ` Michael Ellerman
2015-04-17 4:13 ` Scott Wood
2015-04-17 6:18 ` Michael Ellerman
2015-04-17 18:50 ` Lijun Pan
2015-04-17 18:52 ` Scott Wood
2015-04-18 4:53 ` Lijun Pan
2015-04-18 13:46 ` Timur Tabi
2015-04-20 20:31 ` Scott Wood
2015-04-21 2:02 ` Timur Tabi
2015-04-21 2:09 ` Scott Wood [this message]
2015-04-21 3:42 ` Timur Tabi
2015-04-21 5:01 ` Scott Wood
2015-04-21 13:25 ` Timur Tabi
2015-04-21 17:55 ` Scott Wood
2015-04-21 18:11 ` Timur Tabi
2015-04-21 18:12 ` Scott Wood
2015-04-21 3:27 ` Michael Ellerman
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=1429582152.4352.73.camel@freescale.com \
--to=scottwood@freescale.com \
--cc=Lijun.Pan@freescale.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=richard.schmitt@freescale.com \
--cc=timur@codeaurora.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.