From: Ulf Samuelsson <ulf.samuelsson@atmel.com>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 563] compiling Linux 2.30.2 for ARM with Atmel support
Date: Wed, 12 Aug 2009 12:36:26 +0200 [thread overview]
Message-ID: <4A829B2A.3020901@atmel.com> (raw)
In-Reply-To: <20090812102642.A5E7A77818@busybox.osuosl.org>
bugzilla at busybox.net skrev:
> https://bugs.busybox.net/show_bug.cgi?id=563
>
>
>
>
>
> --- Comment #3 from Olivier Duclos <oduclos@mandriva.com> 2009-08-12 10:26:41 UTC ---
> Thanks. Will the content of this it repo be included in the next stable release
> ?
>
> If you ask, I think buildroot should at least print an error message when
> detecting such incompatibilities.
>
> I've been waisting a lot of time these past few days trying to generate an
> image as I want, but there are so much of bugs and incompatibilities !
>
>
You can apply any patchset you want, the config is just an easy short cut.
When you try to build a non-working patch, you will get your error
message during the patch process.
You should expect the patch to work for the kernel version it was
designed for.
You do have the freedom to test the patch on a later kernel, and
for a range of kernels it will work, but don't expect a patchset
to work for all future versions.
If you want to use a patchset, on a later kernel than what is supported,
then you have to manually adapt the patches to your desired kernel
and then use the custom patch feature.
BR
Ulf Samuelsson
prev parent reply other threads:[~2009-08-12 10:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-11 13:46 [Buildroot] [Bug 563] New: compiling Linux 2.30.2 for ARM with Atmel support bugzilla at busybox.net
2009-08-11 19:45 ` [Buildroot] [Bug 563] " bugzilla at busybox.net
2009-08-11 21:10 ` bugzilla at busybox.net
2009-08-12 10:26 ` bugzilla at busybox.net
2009-08-12 10:36 ` Ulf Samuelsson [this message]
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=4A829B2A.3020901@atmel.com \
--to=ulf.samuelsson@atmel.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