From: Richard Palethorpe <rpalethorpe@suse.de>
To: Cyril Hrubis <chrubis@suse.cz>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH 0/2] Two small fixes for LTP-003
Date: Tue, 30 Nov 2021 14:18:16 +0000 [thread overview]
Message-ID: <87ee6xloas.fsf@suse.de> (raw)
In-Reply-To: <20211130105027.1071-1-chrubis@suse.cz>
Hello,
Pushed, Thanks!
Cyril Hrubis <chrubis@suse.cz> writes:
> This fixes false possitives for tst_fuzzy_sync.h
>
> Cyril Hrubis (2):
> include/tst_fuzzy_sync.h: Add inline to static fucntions
> sparse: Do not report static inline functions
>
> include/tst_fuzzy_sync.h | 14 +++++++-------
> tools/sparse/sparse-ltp.c | 2 +-
> 2 files changed, 8 insertions(+), 8 deletions(-)
>
> --
> 2.32.0
--
Thank you,
Richard.
--
Mailing list info: https://lists.linux.it/listinfo/ltp
prev parent reply other threads:[~2021-11-30 14:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-30 10:50 [LTP] [PATCH 0/2] Two small fixes for LTP-003 Cyril Hrubis
2021-11-30 10:50 ` [LTP] [PATCH 1/2] include/tst_fuzzy_sync.h: Add inline to static fucntions Cyril Hrubis
2021-11-30 11:18 ` Petr Vorel
2021-12-01 7:07 ` Li Wang
2021-11-30 10:50 ` [LTP] [PATCH 2/2] sparse: Do not report static inline functions Cyril Hrubis
2021-11-30 11:21 ` Petr Vorel
2021-11-30 14:18 ` Richard Palethorpe [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=87ee6xloas.fsf@suse.de \
--to=rpalethorpe@suse.de \
--cc=chrubis@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