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 v2 1/3] barebox: add custom version option
Date: Fri, 3 May 2013 12:11:59 +0200	[thread overview]
Message-ID: <20130503121159.41c63ece@skate> (raw)
In-Reply-To: <CAHkwnC-ZiO0Fyd2=QaE8RPuWFfzsf4o_6VUpzVo5tOFLPxMLkA@mail.gmail.com>

Dear Fabio Porcedda,

On Fri, 3 May 2013 11:17:32 +0200, Fabio Porcedda wrote:

> In the patch set v3 barebox is consistent with the kernel.
> 
> If you are speaking just about consistency, I can send a patch for
> U-Boot too. IMHO the kernel way is more flexible, so if we must
> choose only one method, the kernel way is better.
> 
> A problem with having only the latest three version available
> is that barebox and u-boot release frequency are very different.
> Barebox have 12 release per year, U-Boot only 4.
> The latest three release of U-Boot cover nine months but the latest
> three release of barebox cover only three months.
> So if a defconfig use a specific barebox version, that defconfig can
> be used only for three months.
> I think that three months is not enough.

I think what you say makes sense.

> It's better if i send patch for U-Boot too?

Yes. I would however maybe wait for the opinion of others like Arnout,
Peter or Gustavo. Maybe they disagree with my opinion, and I don't want
you to do extra work that may not be accepted in the end.

Best regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  reply	other threads:[~2013-05-03 10:11 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-17  7:41 [Buildroot] [PATCH v2 0/3] barebox new option and new boards Fabio Porcedda
2013-04-17  7:41 ` [Buildroot] [PATCH v2 1/3] barebox: add custom version option Fabio Porcedda
2013-05-01 21:10   ` Thomas Petazzoni
2013-05-03  6:49     ` Fabio Porcedda
2013-05-03  7:57       ` Fabio Porcedda
2013-05-03  8:55       ` Thomas Petazzoni
2013-05-03  9:17         ` Fabio Porcedda
2013-05-03 10:11           ` Thomas Petazzoni [this message]
2013-05-03 16:46           ` Arnout Vandecappelle
2013-05-06 14:15             ` Peter Korsgaard
2013-05-03 10:50       ` Peter Korsgaard
2013-05-03 11:26         ` Fabio Porcedda
2013-04-17  7:41 ` [Buildroot] [PATCH v2 2/3] configs: add defconfig for Telit EVK-PRO3 Fabio Porcedda
2013-05-01 21:13   ` Thomas Petazzoni
2013-05-01 22:14     ` Fabio Porcedda
2013-05-02  9:58       ` Thomas Petazzoni
2013-04-17  7:41 ` [Buildroot] [PATCH v2 3/3] configs: add defconfig for Atmel AT91SAM9260-EK Nand Flash Boot Fabio Porcedda
2013-05-01 21:14   ` Thomas Petazzoni
2013-05-01 22:04     ` Fabio Porcedda
2013-05-02  9:59       ` Thomas Petazzoni
2013-05-01  6:57 ` [Buildroot] [PATCH v2 0/3] barebox new option and new boards Fabio Porcedda
2013-05-03  8:24   ` Fabio Porcedda

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=20130503121159.41c63ece@skate \
    --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