From: Petr Vorel <pvorel@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH 1/1] Remove break after return
Date: Fri, 5 Apr 2019 08:56:09 +0200 [thread overview]
Message-ID: <20190405065609.GA26076@dell5510> (raw)
In-Reply-To: <5CA6C9F7.1060907@cn.fujitsu.com>
Hi Xiao,
> I have added libc sigpending() detection by the following patch:
> http://lists.linux.it/pipermail/ltp/2019-April/011590.html
> Perhaps, we should avoid potential compiler warnings by keeping the
> break here.
Oh yes, adding break after tst_brk in [1] (in case of #ifndef HAVE_STIME) is correct.
Kind regards,
Petr
[1] https://patchwork.ozlabs.org/patch/1077969/
prev parent reply other threads:[~2019-04-05 6:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-28 10:50 [LTP] [PATCH 1/1] Remove break after return Petr Vorel
2019-03-28 10:59 ` Enji Cooper
2019-03-29 3:04 ` Xiao Yang
2019-04-03 12:02 ` Cyril Hrubis
2019-04-03 12:06 ` Petr Vorel
2019-04-04 1:29 ` Xiao Yang
2019-04-05 6:48 ` Petr Vorel
2019-04-05 3:22 ` Xiao Yang
2019-04-05 6:56 ` Petr Vorel [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=20190405065609.GA26076@dell5510 \
--to=pvorel@suse.cz \
--cc=ltp@lists.linux.it \
/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