From: Bernhard Fischer <rep.dot.nop@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] AVR32 patch (& others)
Date: Sun, 28 Jan 2007 16:25:32 +0100 [thread overview]
Message-ID: <20070128152531.GR28221@aon.at> (raw)
In-Reply-To: <563e01c742e2$fb5b8670$dcc4af0a@atmel.com>
On Sun, Jan 28, 2007 at 02:38:00PM +0100, Ulf Samuelsson wrote:
>Hi Bernard,
>You said that you would commit the prepatory AVR32 patch as soon as
>the confusion of multiple sends was sorted out.
.. and as soon as other stuff which went in my queue earlier is done (or
any other stuff i decide to do for that matter. I do not mean to sound
harsh, but remember that i'm not one of those timesys people who get
money for providing support for Atmel. It is my time, i don't have any
board you're adding to play with, so my interrest in helping you is
purely voluntarily. Please keep this in mind, thanks).
Merged anyway (hope i picked the correct version. It would help if you
could put numbers in your patches, like, e.g.:
Atmel_Config.in.02.patch or the like.). Thanks.
>Still any problems?
>
>Also:
> No reply on the "BSP" patch, the "TARGET_CFLAGS" and the "local" patches.
BSP is a bug squashing party. It's fun but i don't want to party right
now ;)
The TARGET_CFLAGS is something that doesn't sound clean to me, fwiw:
Put them into TARGET_CONFIGURE_OPTS for a start. Then build _all_
packages to see if you broke something. For those packages that still do
not pick up the TARGET_CFLAGS properly, additionally pass
TARGET_CONFIGURE_OPTS to the $(MAKE) in the respective packages I'd say.
prev parent reply other threads:[~2007-01-28 15:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070128002047.841C748581@busybox.net>
[not found] ` <200701280208.43998.vda.linux@googlemail.com>
[not found] ` <20070128111333.GO28221@aon.at>
2007-01-28 13:38 ` [Buildroot] AVR32 patch (& others) Ulf Samuelsson
2007-01-28 15:25 ` Bernhard Fischer [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=20070128152531.GR28221@aon.at \
--to=rep.dot.nop@gmail.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