From: Olaf Hering <olaf@aepfle.de>
To: Andres Lagar-Cavilla <andres@lagarcavilla.org>
Cc: xen-devel@lists.xen.org
Subject: Re: tools/memshr: fix build errors caused by Werror
Date: Wed, 28 Mar 2012 18:51:09 +0200 [thread overview]
Message-ID: <20120328165109.GA26888@aepfle.de> (raw)
In-Reply-To: <1830e1c0c859a151f0dba58157e28695.squirrel@webmail.lagarcavilla.org>
On Wed, Mar 28, Andres Lagar-Cavilla wrote:
> > tools/memshr: fix build errors caused by Werror
> > shm.c:85: error: 'shm_area_close' defined but not used
> >
> > Mark fingerprint functions as inline, remove unused shm_area_close.
>
> This looks mostly good except for ....
I will resend this patch without the change to shm_area_close.
Since the tree has alot more issues with -Werror my EXTRA_CFLAGS patch
has to be used with -Wno-error for the time being until issues like this
are resolved with a suitable change.
Olaf
prev parent reply other threads:[~2012-03-28 16:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.937.1332944441.1399.xen-devel@lists.xen.org>
2012-03-28 14:42 ` tools/memshr: fix build errors caused by Werror Andres Lagar-Cavilla
2012-03-28 16:51 ` Olaf Hering [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=20120328165109.GA26888@aepfle.de \
--to=olaf@aepfle.de \
--cc=andres@lagarcavilla.org \
--cc=xen-devel@lists.xen.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;
as well as URLs for NNTP newsgroup(s).