From: Hans-Christian Egtvedt <hcegtvedt@norway.atmel.com>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit:trunk/buildroot/target/device/Atmel/Linux:kernel-patches-2.6.22.1
Date: Thu, 26 Jul 2007 09:01:16 +0200 [thread overview]
Message-ID: <1185433276.31437.32.camel@localhost.localdomain> (raw)
In-Reply-To: <46A3D08D.4070505@tait.co.nz>
On Mon, 2007-07-23 at 09:47 +1200, Robin Gilks wrote:
> ulf at uclibc.org wrote:
> > Author: ulf
> > Date: 2007-07-20 01:27:49 -0700 (Fri, 20 Jul 2007)
> > New Revision: 19172
> >
> > Log:
> > Add patch for linux 2.6.22.1
> >
> > Added:
> > trunk/buildroot/target/device/Atmel/Linux/kernel-patches-2.6.22.1/
> > trunk/buildroot/target/device/Atmel/Linux/kernel-patches-2.6.22.1/2.6.22.1-atmel.patch
> >
> >
> > Changeset:
> >
> > Sorry, the patch is too large to include (9725 lines).
> > Please use ViewCVS to see it!
> >
> > http://uclibc.org/cgi-bin/viewcvs.cgi?view=rev&root=svn&rev=19172
>
> Is there any differentiation between different families of Atmel CPU in
> the buildroot tree? i.e. does this patchset only apply to AT91 series or
> does it include AVR32?
Why is these patches not in the kernel-headers directory?
Speaking for the AVR32 support I do not need a separate directory for
AVR32 specific patches. I put all the patches in
toolchain/kernel-headers.
--
With kind regards,
Hans-Christian Egtvedt, siv.ing. (M.Sc.)
Applications Engineer - AVR32 System Solutions - Atmel Norway
--
Mvh
Hans-Christian Egtvedt
prev parent reply other threads:[~2007-07-26 7:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-20 8:27 [Buildroot] svn commit: trunk/buildroot/target/device/Atmel/Linux: kernel-patches-2.6.22.1 ulf at uclibc.org
2007-07-22 21:47 ` [Buildroot] svn commit:trunk/buildroot/target/device/Atmel/Linux:kernel-patches-2.6.22.1 Robin Gilks
2007-07-22 22:51 ` [Buildroot] svncommit:trunk/buildroot/target/device/Atmel/Linux:kernel-patches-2.6.22.1 Ulf Samuelsson
2007-07-26 7:01 ` Hans-Christian Egtvedt [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=1185433276.31437.32.camel@localhost.localdomain \
--to=hcegtvedt@norway.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