From: ulf at uclibc.org <ulf@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot/target/device/Atmel: arch-avr32 arch-avr32/kernel-patches-2.6 etc...
Date: Thu, 10 Jul 2008 08:15:52 -0700 (PDT) [thread overview]
Message-ID: <20080710151552.9DECC3C6B6@busybox.net> (raw)
Author: ulf
Date: 2008-07-10 08:15:52 -0700 (Thu, 10 Jul 2008)
New Revision: 22763
Log:
Add AVR32 patches for 2.6.25.10
Added:
trunk/buildroot/target/device/Atmel/arch-avr32/kernel-patches-2.6.25.10/
trunk/buildroot/target/device/Atmel/arch-avr32/kernel-patches-2.6.25.10/linux-2.6.25.10.atmel.2.patch.bz2
trunk/buildroot/target/device/Atmel/atngw100-expanded/atngw100-expanded-linux-2.6.25.10.config
Modified:
trunk/buildroot/target/device/Atmel/arch-avr32/Config.in.linux.patches
Changeset:
Sorry, the patch is too large to include (1319 lines).
Please use ViewCVS to see it!
http://uclibc.org/cgi-bin/viewcvs.cgi?view=rev&root=svn&rev=22763
next reply other threads:[~2008-07-10 15:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-10 15:15 ulf at uclibc.org [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-08-19 22:43 [Buildroot] svn commit: trunk/buildroot/target/device/Atmel: arch-avr32 arch-avr32/kernel-patches-2.6 etc 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=20080710151552.9DECC3C6B6@busybox.net \
--to=ulf@uclibc.org \
--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