From: Ivan Kuten <ivan.kuten@promwad.com>
To: buildroot@busybox.net
Subject: [Buildroot] Adding Cirrus EP93XX ARM to buildroot
Date: Thu, 04 Oct 2007 01:54:57 +0300 [thread overview]
Message-ID: <47041DC1.8020301@promwad.com> (raw)
In-Reply-To: <20071003204012.GE20951@aon.at>
> 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.
Cirrus Patches may be not a part of buildroot but refer as URL on Cirrus web site.
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.
Best regards,
Ivan
--------------------------------
Embedded Linux engineer,
Promwad Company: http://www.promwad.com/
Homepage : http://www.ivankuten.com/
--------------------------------
next prev parent reply other threads:[~2007-10-03 22:54 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 [this message]
2007-10-04 4:08 ` Ulf Samuelsson
2007-10-04 13:46 ` Brian Austin
2007-10-06 20:15 ` Bernhard Fischer
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=47041DC1.8020301@promwad.com \
--to=ivan.kuten@promwad.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