From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot/target/device/Atmel/arch-avr32: kernel-patches-2.6.27.6
Date: Tue, 23 Dec 2008 10:48:45 +0100 [thread overview]
Message-ID: <873agf8bnm.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <20081220221939.4935476CEB@busybox.osuosl.org> (ulf@uclibc.org's message of "Sat\, 20 Dec 2008 22\:19\:39 +0000 \(UTC\)")
>>>>> "ulf" == ulf <ulf@uclibc.org> writes:
ulf> Author: ulf
ulf> Date: 2008-12-20 22:19:38 +0000 (Sat, 20 Dec 2008)
ulf> New Revision: 24469
ulf> Log:
ulf> Add 2.6.27.7 patches for AVR32
ulf> Added:
ulf> trunk/buildroot/target/device/Atmel/arch-avr32/kernel-patches-2.6.27.6/
2.6.27.6 or 2.6.27.7? Don't they apply to 2.6.27.10?
Do we really need another ~800kb of avr specific patches? What about
the older patches, can they go away?
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2008-12-23 9:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-20 22:19 [Buildroot] svn commit: trunk/buildroot/target/device/Atmel/arch-avr32: kernel-patches-2.6.27.6 ulf at uclibc.org
2008-12-23 9:48 ` Peter Korsgaard [this message]
2009-01-02 22:44 ` [Buildroot] svn commit:trunk/buildroot/target/device/Atmel/arch-avr32:kernel-patches-2.6.27.6 Ulf Samuelsson
2009-01-03 7:58 ` Peter Korsgaard
2009-01-03 9:33 ` Ulf Samuelsson
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=873agf8bnm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.