Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Bernhard Fischer <rep.dot.nop@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Adding Cirrus  EP93XX  ARM to buildroot
Date: Sat, 6 Oct 2007 22:15:36 +0200	[thread overview]
Message-ID: <20071006201536.GH20951@aon.at> (raw)
In-Reply-To: <003c01c8063e$26e48a70$b07ee255@atmel.com>

On Thu, Oct 04, 2007 at 06:08:55AM +0200, Ulf Samuelsson wrote:
>> 
>>> Depends a bit.. From the sounds, all but the configs should reside in
>>> generic parts.
>>> That said, I'm not too keen on building up a shadow of kernel.org, so
>>> please
>>> 1) update your patches against current linus tree (or -mm, however you
>>> see fit)
>>> 2) submit your patches upstream
>> 
>> Bernhard,
>> 
>> Let me not argee here. You are forcing "keep up-to-date" policy instead of
>> "stable release" policy.

How so? I'm asking that you submit your patches to the respective
upstream maintainers for review and later inclusion.

>> Cirrus Patches may be not a part of buildroot but refer as URL on Cirrus web site.

This is an entirely different thing.

>> In embedded world is it often that you have to stick to some old kernel version because
>> of dependency on 3rd components specific to that particular kernel version.
>> 
>> Take into account reasoning of usual linux developer - I do not want to update my kernel
>> patches for every (month,week) -mm released. I want to have a stable base - which remains stable
>> after half-of-year.
>> 
>> And submitting patches to mainstream takes long time. And we want Cirrus support now.

Supporting some old version of packages with supplemental patches is
fine and one thing. Refusing even try to get your additions merged is
not a proper thing to do IMO.

It is extremely burdensome and impractical to have to patch every single
"new" upstream release (let alone time-consuming and thus probably
expensive if somebody pays the time you're spending on doing it).

>> Best regards,
>> Ivan

>Bernard wants you to freeze the buildroot source code for a specific customer.

Ulf, please stop to babble such crap. There is /dev/null for such
insults. Thank you.

  parent reply	other threads:[~2007-10-06 20:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-02 21:51 [Buildroot] Adding Cirrus EP93XX ARM to buildroot Brian Austin
2007-10-02 23:42 ` Ivan Kuten
2007-10-03 20:40   ` Bernhard Fischer
2007-10-03 22:54     ` Ivan Kuten
2007-10-04  4:08       ` Ulf Samuelsson
2007-10-04 13:46         ` Brian Austin
2007-10-06 20:15         ` Bernhard Fischer [this message]
2007-10-07 17:45           ` Ivan Kuten
2007-10-07 17:00             ` Bernhard Fischer

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=20071006201536.GH20951@aon.at \
    --to=rep.dot.nop@gmail.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