public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Matthias Fischer <matthias.fischer@ipfire.org>
To: development@lists.ipfire.org
Subject: Warnings about unused variables (was: Re: [PATCH] dnsmasq 2.75: next patch... (No.50))
Date: Sat, 06 Feb 2016 12:37:29 +0100	[thread overview]
Message-ID: <56B5DAF9.4020003@ipfire.org> (raw)
In-Reply-To: <1454629841.10195.57.camel@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 446 bytes --]

Hi,

On 05.02.2016 00:50, Michael Tremer wrote:
> Get in touch with Simon for this. It is nothing major. But good to
> point it out.

For the records:
The (two) warnings about "unused variables' are ONLY triggered when
deactivating DHCP in lfs-file through:

...
-e 's|#define HAVE_DHCP|//#define HAVE_DHCP|g' \
...

No other warnings or errors occured during my tests.

I asked about this in the dnsmasq mailing list. We'll see.

Best,
Matthias

  parent reply	other threads:[~2016-02-06 11:37 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-17 14:30 [PATCH] dnsmasq 2.75: next patch... (No.50) Matthias Fischer
2016-01-19  7:39 ` R. W. Rodolico
2016-01-19 19:59   ` Matthias Fischer
2016-01-19 21:27     ` R. W. Rodolico
2016-01-20 20:29       ` Matthias Fischer
2016-01-20 18:23     ` Kienker, Fred
2016-01-20 18:58       ` R. W. Rodolico
2016-01-20 23:51         ` Michael Tremer
2016-01-21  3:39           ` R. W. Rodolico
2016-01-23 12:00           ` Matthias Fischer
2016-02-04 20:58             ` R. W. Rodolico
2016-02-04 23:50             ` Michael Tremer
2016-02-05 22:45               ` Matthias Fischer
2016-02-05 22:50                 ` Kienker, Fred
2016-02-06 11:37               ` Matthias Fischer [this message]
2016-01-20 20:36       ` Matthias Fischer

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=56B5DAF9.4020003@ipfire.org \
    --to=matthias.fischer@ipfire.org \
    --cc=development@lists.ipfire.org \
    /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