From: Richard Weinberger <richard@nod.at>
To: Lorenzo Colitti <lorenzo@google.com>
Cc: Erik Kline <ek@google.com>,
"user-mode-linux-devel@lists.sourceforge.net"
<user-mode-linux-devel@lists.sourceforge.net>
Subject: Re: [uml-devel] Warning in syscall_trace_enter
Date: Tue, 03 Mar 2015 09:48:57 +0100 [thread overview]
Message-ID: <54F57579.9@nod.at> (raw)
In-Reply-To: <CAKD1Yr2s_KFBv_GZipeeRDY+MkpLkMHahhdkOReqdSQy5ifhLA@mail.gmail.com>
Am 03.03.2015 um 09:39 schrieb Lorenzo Colitti:
> On Tue, Mar 3, 2015 at 5:32 PM, Richard Weinberger
> <richard.weinberger@gmail.com> wrote:
>> IIRC the big plan is to make tracehook_report_syscall_entry() tree-wide void.
>
> Ack, thanks. In the meantime, for trees we already build with -Werror,
> we'll put a temporary local hack in place.
As long GCC has a shitload of completely useless warnings building with -Werror
is just a PITA. That's why Linux does not use that flag. :-)
Thanks,
//richard
------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the
conversation now. http://goparallel.sourceforge.net/
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2015-03-03 9:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-03 4:55 [uml-devel] Warning in syscall_trace_enter Lorenzo Colitti
2015-03-03 8:32 ` Richard Weinberger
2015-03-03 8:39 ` Lorenzo Colitti
2015-03-03 8:48 ` Richard Weinberger [this message]
2015-03-03 9:26 ` Geert Uytterhoeven
2015-03-03 9:29 ` Richard Weinberger
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=54F57579.9@nod.at \
--to=richard@nod.at \
--cc=ek@google.com \
--cc=lorenzo@google.com \
--cc=user-mode-linux-devel@lists.sourceforge.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.