public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier.adi@gmail.com>
To: "Biefel, Reiner (NSN - DE/Munich)" <reiner.biefel@nsn.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: Compile Error: structure has no member named lowest_vol_num
Date: Fri, 3 Jul 2009 03:19:25 -0400	[thread overview]
Message-ID: <8bd0f97a0907030019n24344aaewdbc19b33789ed5e8@mail.gmail.com> (raw)
In-Reply-To: <077E41CFFD002C4CAB7DFA4386A53264F5D814@DEMUEXC014.nsn-intra.net>

On Fri, Jul 3, 2009 at 03:17, Biefel, Reiner wrote:
>>they either have then in the standard path like a sane toolchain, or
>>they use CFLAGS.  i'm not saying putting -I flags in CFLAGS vs
>>CPPFLAGS is correct, just that people rarely do it the right way.
>
> Does this mean, if I had used CFLAGS instead CPPFLAGS I don't need your
> patch?

probably, but considering you're one of the few people using the right
variable for its intended purpose, why stop now ? ;)
-mike

  reply	other threads:[~2009-07-03  7:19 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-25 12:12 Compile Error: structure has no member named lowest_vol_num Biefel, Reiner (NSN - DE/Munich)
2009-06-29  7:29 ` Biefel, Reiner (NSN - DE/Munich)
2009-06-30 11:45   ` Artem Bityutskiy
2009-06-30 14:27     ` Biefel, Reiner (NSN - DE/Munich)
2009-06-30 14:44 ` Artem Bityutskiy
2009-07-02  1:15   ` Mike Frysinger
2009-07-03  6:52     ` Artem Bityutskiy
2009-07-03  7:00       ` Biefel, Reiner (NSN - DE/Munich)
2009-07-03  7:02         ` Mike Frysinger
2009-07-03  7:08           ` Biefel, Reiner (NSN - DE/Munich)
2009-07-03  7:12             ` Mike Frysinger
2009-07-03  7:17               ` Biefel, Reiner (NSN - DE/Munich)
2009-07-03  7:19                 ` Mike Frysinger [this message]
2009-07-03  7:22     ` Artem Bityutskiy
2009-07-03  7:41     ` Artem Bityutskiy

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=8bd0f97a0907030019n24344aaewdbc19b33789ed5e8@mail.gmail.com \
    --to=vapier.adi@gmail.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=reiner.biefel@nsn.com \
    /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