From: Ulf Samuelsson <ulf.samuelsson@atmel.com>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot: target/device/Atmel/arch-avr32/kernel-pa etc...
Date: Fri, 30 Jan 2009 21:05:10 +0100 [thread overview]
Message-ID: <1233345910.4147.99.camel@elrond.atmel.com> (raw)
In-Reply-To: <877i4cmw4p.fsf@macbook.be.48ers.dk>
fre 2009-01-30 klockan 20:28 +0100 skrev Peter Korsgaard:
> >>>>> "Ulf" == Ulf Samuelsson <ulf.samuelsson@atmel.com> writes:
>
> Hi,
>
> Ulf> HC has all these patches in the kernel-headers directory in his
> Ulf> tree. I thought initially that was a little risky.
>
> Ulf> I therefore tried putting them in the avr32 specific parts,
> Ulf> but I have seen strange effects on some packages.
> Ulf> That is why I tried this approach.
>
> Just split up the patches and put the kernel header _FIXES_ in
> toolchain/kernel-headers, just like all other architectures do.
>
> The leftovers you can but under target/device/Atmel.
>
> Ulf> Have read a little bit more on the kernel-headers,
> Ulf> and it appears that I can keep the stuff in the
> Ulf> AVR32 parts and then define
>
> Ulf> KERNEL_HEADERS_PATCH_DIR=target/device/Atmel/arch-avr32/2.6.[27.6|28.2]
>
> Ulf> for AVR32 targets.
>
> Ulf> Does that make sense?
>
> I would prefer to have the kernel headers stuff together for all
> archs, the amount (and size of) patches is normally very limited.
>
Since HC has direct contact with the tool guys,
I will let him decide and implement.
One of the patches which was needed, is the largest one.
BR
Ulf Samuelsson
prev parent reply other threads:[~2009-01-30 20:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-30 8:53 [Buildroot] svn commit: trunk/buildroot: target/device/Atmel/arch-avr32/kernel-pa etc ulf at uclibc.org
2009-01-30 9:04 ` Peter Korsgaard
2009-01-30 9:09 ` Hans-Christian Egtvedt
2009-01-30 9:21 ` Peter Korsgaard
2009-01-30 17:49 ` Ulf Samuelsson
2009-01-30 19:28 ` Peter Korsgaard
2009-01-30 20:05 ` 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=1233345910.4147.99.camel@elrond.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