From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot/target/device/Atmel: atstk100x
Date: Thu, 29 Jan 2009 10:52:58 +0100 [thread overview]
Message-ID: <87iqnytp51.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <20090129104341.2d34aa8e@hcegtvedt> (Hans-Christian Egtvedt's message of "Thu\, 29 Jan 2009 10\:43\:41 +0100")
>>>>> "Hans-Christian" == Hans-Christian Egtvedt <hans-christian.egtvedt@atmel.com> writes:
>> Too configs for practically the same kernel version? That doesn't
>> sound right.
>>
Hans-Christian> You can do "make atstk1005_defconfig" and similar for
Hans-Christian> most of the AVR32 boards. The defconfig in the kernel
Hans-Christian> is quite sane.
So in other words these files should go away?
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2009-01-29 9:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-29 9:33 [Buildroot] svn commit: trunk/buildroot/target/device/Atmel: atstk100x ulf at uclibc.org
2009-01-29 9:38 ` Peter Korsgaard
2009-01-29 9:43 ` Hans-Christian Egtvedt
2009-01-29 9:52 ` Peter Korsgaard [this message]
2009-01-29 9:59 ` Hans-Christian Egtvedt
2009-01-29 18:01 ` Ulf Samuelsson
2009-01-30 8:09 ` Hans-Christian Egtvedt
2009-01-30 8:52 ` Peter Korsgaard
2009-01-30 9:05 ` Ulf Samuelsson
2009-01-30 9:14 ` Hans-Christian Egtvedt
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=87iqnytp51.fsf@macbook.be.48ers.dk \
--to=jacmet@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