From: Hans-Christian Egtvedt <hans-christian.egtvedt@atmel.com>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot/target/device/Atmel/arch-avr32/kernel-patches-2.6.25.10
Date: Fri, 11 Jul 2008 07:38:29 +0200 [thread overview]
Message-ID: <1215754709.11647.62.camel@localhost> (raw)
In-Reply-To: <20080710161237.B4EDD3C642@busybox.net>
On Thu, 2008-07-10 at 09:12 -0700, ulf at uclibc.org wrote:
> Author: ulf
> Date: 2008-07-10 09:12:36 -0700 (Thu, 10 Jul 2008)
> New Revision: 22766
>
> Log:
> Do not use a localversion of kernel, to allow modules to be installed in the correct directory
>
I do not like this approach, users will think they are running an
upstream kernel while they are really not. The Atmel-kernel is quite
different from upstream.
I have a fix for localversion in my GIT tree, I will send that patch to
this list for review. I just need to sort out an issue with the modules
being installed again for every make.
<snipp>
--
With kind regards,
Hans-Christian Egtvedt, Applications Engineer
prev parent reply other threads:[~2008-07-11 5:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-10 16:12 [Buildroot] svn commit: trunk/buildroot/target/device/Atmel/arch-avr32/kernel-patches-2.6.25.10 ulf at uclibc.org
2008-07-11 5:38 ` Hans-Christian Egtvedt [this message]
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=1215754709.11647.62.camel@localhost \
--to=hans-christian.egtvedt@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