From: Ulf Samuelsson <ulf.samuelsson@atmel.com>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot/target/device/Atmel:at91rm9200df at91sam9260dfc at91sam9260p etc...
Date: Tue, 11 Mar 2008 19:56:26 +0100 [thread overview]
Message-ID: <014401c883af$e519d510$080514ac@atmel.com> (raw)
In-Reply-To: 20080311162106.4D4D3120150@busybox.net
This is wrong.
The AT91 chips either use the "Linux" subdirectory, when there is a common
patchset with the AVR32,or "arch-arm" when it is only AT91 related.
An AVR32 only patch will reside in "arch-avr32"
Best Regards
Ulf Samuelsson
----- Original Message -----
From: <ninevoltz@uclibc.org>
To: <buildroot@uclibc.org>
Sent: Tuesday, March 11, 2008 5:21 PM
Subject: [Buildroot] svn commit: trunk/buildroot/target/device/Atmel:at91rm9200df at91sam9260dfc at91sam9260p etc...
> Author: ninevoltz
> Date: 2008-03-11 09:21:05 -0700 (Tue, 11 Mar 2008)
> New Revision: 21296
>
> Log:
> added kernel-patches directories
>
> Added:
> trunk/buildroot/target/device/Atmel/at91rm9200df/kernel-patches/
> trunk/buildroot/target/device/Atmel/at91sam9260dfc/kernel-patches/
> trunk/buildroot/target/device/Atmel/at91sam9260pf/kernel-patches/
> trunk/buildroot/target/device/Atmel/at91sam9261ek/kernel-patches/
> trunk/buildroot/target/device/Atmel/at91sam9263ek/kernel-patches/
>
>
> Changeset:
> _______________________________________________
> buildroot mailing list
> buildroot at uclibc.org
> http://busybox.net/mailman/listinfo/buildroot
>
next prev parent reply other threads:[~2008-03-11 18:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-11 16:21 [Buildroot] svn commit: trunk/buildroot/target/device/Atmel: at91rm9200df at91sam9260dfc at91sam9260p etc ninevoltz at uclibc.org
2008-03-11 18:56 ` Ulf Samuelsson [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-01-03 16:10 ulf at uclibc.org
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='014401c883af$e519d510$080514ac@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