From: David Fernandez <david.fernandez.work@googlemail.com>
To: eCos development list <ecos-devel@ecos.sourceware.org>
Cc: Simon Kallweit <simon.kallweit@intefo.ch>,
John Dallaway <jld@ecoscentric.com>,
John Eigelaar <john@kses.net>
Subject: Re: lwIP upgrade to CVS HEAD
Date: Thu, 14 May 2009 13:27:00 -0000 [thread overview]
Message-ID: <ea104e1b0905140626j65546c6fs4c2987aadd402eac@mail.gmail.com> (raw)
John Dallaway wrote:
> There's some scope for improving the dependency info. For example,
> CYGIMP_LWIP_MEMP_MEM_MALLOC could specify:
>
> requires { CYGINT_ISO_MEMALLOC != 0 }
> default_value { CYGINT_ISO_MEMALLOC != 0 }
>
Shouldn't it use "calculated_value" instead of "default_value"?
Cheers
next reply other threads:[~2009-05-14 13:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-14 13:27 David Fernandez [this message]
2009-05-14 13:31 ` Simon Kallweit
[not found] <49F83C8B.9000108@intefo.ch>
2009-05-05 10:31 ` John Dallaway
2009-05-05 11:29 ` Simon Kallweit
2009-05-08 15:56 ` John Dallaway
2009-05-13 16:03 ` Simon Kallweit
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=ea104e1b0905140626j65546c6fs4c2987aadd402eac@mail.gmail.com \
--to=david.fernandez.work@googlemail.com \
--cc=ecos-devel@ecos.sourceware.org \
--cc=jld@ecoscentric.com \
--cc=john@kses.net \
--cc=simon.kallweit@intefo.ch \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).