From: Richard Weinberger <richard@nod.at>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Lorenzo Colitti <lorenzo@google.com>, 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 10:29:12 +0100 [thread overview]
Message-ID: <54F57EE8.3030609@nod.at> (raw)
In-Reply-To: <CAMuHMdWw6ZoqD5tmA1QhmYZfvvLXX=wb_Ux-h+xhGWjepVRRUQ@mail.gmail.com>
Am 03.03.2015 um 10:26 schrieb Geert Uytterhoeven:
> On Tue, Mar 3, 2015 at 9:48 AM, Richard Weinberger <richard@nod.at> wrote:
>> 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. :-)
>
> For some classes of warnings yet.
>
> For this particular case, given the tree-wide void plan, it can easily be
> resolved by dropping the __must_check attribute from
> tracehook_report_syscall_entry() now.
Yep. Currently I'm searching the archives for that plan.
I was about to fix that warning a few months ago but I was told
that is not needed...
Thanks,
//richard
prev parent reply other threads:[~2015-03-03 9:29 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
2015-03-03 9:26 ` Geert Uytterhoeven
2015-03-03 9:29 ` Richard Weinberger [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=54F57EE8.3030609@nod.at \
--to=richard@nod.at \
--cc=ek@google.com \
--cc=geert@linux-m68k.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox