All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot: target/device/Atmel/arch-avr32/kernel-pa etc...
Date: Fri, 30 Jan 2009 10:04:11 +0100	[thread overview]
Message-ID: <87zlh9np10.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <20090130085310.9730F765E9@busybox.osuosl.org> (ulf@uclibc.org's message of "Fri\, 30 Jan 2009 08\:53\:10 +0000 \(UTC\)")

>>>>> "ulf" == ulf  <ulf@uclibc.org> writes:

 ulf> Author: ulf
 ulf> Date: 2009-01-30 08:53:08 +0000 (Fri, 30 Jan 2009)
 ulf> New Revision: 25157

 ulf> Log:
 ulf> Move AVR32 patch to kernel header to unbreak several applications

What does these do and what applications are unbroken by them? Could
you please write more detailed commit messages?

 ulf> Added:
 ulf>    trunk/buildroot/toolchain/kernel-headers/linux-2.6.28.2-100-avr32.patch

What does this do to the headers?

 ulf>    trunk/buildroot/toolchain/kernel-headers/linux-2.6.28.2-201-avr32-atmel_mpopfb-disable-debug.patch

That seems completely unrelated to kernel headers.

 ulf>    trunk/buildroot/toolchain/kernel-headers/linux-2.6.28.2-202-avr32-atmel_mpopfb-add-signal-to-disable-line-caching.patch

This one as well.

 ulf>    trunk/buildroot/toolchain/kernel-headers/linux-2.6.28.2-203-avr32-fix-arch-header-byteorder.patch

OK.

 ulf>    trunk/buildroot/toolchain/kernel-headers/linux-2.6.28.2-204-avr32-ap700x-fix-det_pin-for-nand-flash.patch

That also seems unrelated.

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2009-01-30  9:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-30  8:53 [Buildroot] svn commit: trunk/buildroot: target/device/Atmel/arch-avr32/kernel-pa etc ulf at uclibc.org
2009-01-30  9:04 ` Peter Korsgaard [this message]
2009-01-30  9:09   ` Hans-Christian Egtvedt
2009-01-30  9:21     ` Peter Korsgaard
2009-01-30 17:49     ` Ulf Samuelsson
2009-01-30 19:28       ` Peter Korsgaard
2009-01-30 20:05         ` 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=87zlh9np10.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.