Netdev List
 help / color / mirror / Atom feed
From: Alexei Starovoitov <ast@fb.com>
To: Song Liu <songliubraving@fb.com>, Cong Wang <xiyou.wangcong@gmail.com>
Cc: kbuild test robot <lkp@intel.com>,
	David Miller <davem@davemloft.net>,
	"kbuild-all@01.org" <kbuild-all@01.org>,
	"alexei.starovoitov@gmail.com" <alexei.starovoitov@gmail.com>,
	Martin Lau <kafai@fb.com>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"liu.song.a23@gmail.com" <liu.song.a23@gmail.com>
Subject: Re: [PATCH net-next] tcp: add tracepoint trace_tcp_retransmit_synack()
Date: Fri, 27 Oct 2017 12:57:53 -0700	[thread overview]
Message-ID: <6257e78f-4423-ddd3-422d-2bd818a83be0@fb.com> (raw)
In-Reply-To: <D81267F3-4447-4375-B2A8-06F92FAF4ACD@fb.com>

On 10/26/17 10:06 PM, Song Liu wrote:
>
>> On Oct 26, 2017, at 7:01 PM, Cong Wang <xiyou.wangcong@gmail.com> wrote:
>>
>> On Thu, Oct 26, 2017 at 4:50 PM, Song Liu <songliubraving@fb.com> wrote:
>>> In this case, we are putting CONFIG_IPV6 in TRACE_EVENT macro, which generates
>>> warnings like:
>>>
>>> ./include/trace/events/tcp.h:274:1: error: directive in argument list
>>> ./include/trace/events/tcp.h:281:1: error: directive in argument list
>>>
>>> Seems these warning cannot be easily avoided. This is also the same pattern we
>>> have been using in include/trace/events/tcp.h.
>>
>> Hmm, we use the same so why it only complains about this one?\
>
> sparse reports same warning for all the lines in tcp.h. Don't know why
> kbuild test bot only complains about this patch.

it's safe to ignore this sparse error.
The #ifdef inside TP_fast_assign() in net.h have been there for years
without issues.
$ make C=2 net/core/dev.o
../include/trace/events/net.h:170:1: error: directive in argument list
../include/trace/events/net.h:172:1: error: directive in argument list
../include/trace/events/net.h:174:1: error: directive in argument list

  reply	other threads:[~2017-10-27 19:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-24 23:57 [PATCH net-next] tcp: add tracepoint trace_tcp_retransmit_synack() Song Liu
2017-10-25 16:17 ` Song Liu
2017-10-26  3:13 ` kbuild test robot
2017-10-26 23:50   ` Song Liu
2017-10-27  2:01     ` Cong Wang
2017-10-27  5:06       ` Song Liu
2017-10-27 19:57         ` Alexei Starovoitov [this message]
2017-10-27 20:38 ` Alban Crequy
2017-10-27 20:58   ` Alexei Starovoitov

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=6257e78f-4423-ddd3-422d-2bd818a83be0@fb.com \
    --to=ast@fb.com \
    --cc=alexei.starovoitov@gmail.com \
    --cc=davem@davemloft.net \
    --cc=kafai@fb.com \
    --cc=kbuild-all@01.org \
    --cc=liu.song.a23@gmail.com \
    --cc=lkp@intel.com \
    --cc=netdev@vger.kernel.org \
    --cc=songliubraving@fb.com \
    --cc=xiyou.wangcong@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