mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: treeze.taeung@gmail.com
Cc: ast@kernel.org, daniel@iogearbox.net, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org, qinteng@fb.com
Subject: Re: [PATCH v2 2/4] samples/bpf: Check the result of system()
Date: Thu, 05 Jul 2018 14:24:12 +0900 (KST)	[thread overview]
Message-ID: <20180705.142412.238281898262839575.davem@davemloft.net> (raw)
In-Reply-To: <20180704133639.11855-3-treeze.taeung@gmail.com>

From: Taeung Song <treeze.taeung@gmail.com>
Date: Wed,  4 Jul 2018 22:36:37 +0900

> To avoid the below build warning message,
> use new generate_load() checking the return value.
> 
>   ignoring return value of ‘system’, declared with attribute warn_unused_result
> 
> And it also refactors the duplicate code of both
> test_perf_event_all_cpu() and test_perf_event_task()
> 
> Cc: Teng Qin <qinteng@fb.com>
> Signed-off-by: Taeung Song <treeze.taeung@gmail.com>

Acked-by: David S. Miller <davem@davemloft.net>

  reply	other threads:[~2018-07-05  5:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-04 13:36 [PATCH v2 0/4] samples/bpf: simple fixes Taeung Song
2018-07-04 13:36 ` [PATCH v2 1/4] samples/bpf: add missing <linux/if_vlan.h> Taeung Song
2018-07-05  5:24   ` David Miller
2018-07-04 13:36 ` [PATCH v2 2/4] samples/bpf: Check the result of system() Taeung Song
2018-07-05  5:24   ` David Miller [this message]
2018-07-04 13:36 ` [PATCH v2 3/4] samples/bpf: Check the error of write() and read() Taeung Song
2018-07-05  5:24   ` David Miller
2018-07-04 13:36 ` [PATCH v2 4/4] samples/bpf: add .gitignore file Taeung Song
2018-07-05  5:24   ` David Miller
2018-07-05  8:03 ` [PATCH v2 0/4] samples/bpf: simple fixes Daniel Borkmann

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=20180705.142412.238281898262839575.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=ast@kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=qinteng@fb.com \
    --cc=treeze.taeung@gmail.com \
    /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

all inboxes | Powered by JetHome®