Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] configs: new defconfig for TI am335x-evm
Date: Wed, 21 Sep 2016 12:18:03 +0200	[thread overview]
Message-ID: <20160921121803.487035d8@free-electrons.com> (raw)
In-Reply-To: <87bmzhy6ci.fsf@dell.be.48ers.dk>

Hello,

On Wed, 21 Sep 2016 11:01:17 +0200, Peter Korsgaard wrote:

>  > So maybe it's easier to have separate beaglebone_defconfig (for just
>  > the beaglebone) and am335x_evm_defconfig (for just the EVM), without
>  > trying to have a defconfig that handles multiple boards.  
> 
>  > What do you think?  
> 
> If they are not identical, then yes. Are these minor differences
> critical enough that it makes sense to maintain two defconfigs?

How would you name this common configuration then?

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

  reply	other threads:[~2016-09-21 10:18 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-15 11:51 [Buildroot] [PATCH 1/1] configs: new defconfig for TI am335x-evm Lothar Felten
2016-09-18 17:30 ` Thomas Petazzoni
2016-09-21  7:40   ` Peter Korsgaard
2016-09-21  8:53     ` Thomas Petazzoni
2016-09-21  9:01       ` Peter Korsgaard
2016-09-21 10:18         ` Thomas Petazzoni [this message]
2016-09-21 10:36           ` Peter Korsgaard
2016-09-21 10:55             ` Thomas Petazzoni
2016-09-21 11:23               ` Peter Korsgaard
2016-09-21 12:09             ` Thomas Petazzoni
2016-09-22 22:21               ` Lothar Felten
2016-09-23  5:47                 ` Thomas Petazzoni
2016-09-23  6:50                 ` Peter Korsgaard

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=20160921121803.487035d8@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.net \
    /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