[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAM_iQpVzGpype9ytprzF9zcigZ6ckE03SYnGPdfSxUQRgqV82Q@mail.gmail.com>
Date: Thu, 26 Oct 2017 19:01:26 -0700
From: Cong Wang <xiyou.wangcong@...il.com>
To: Song Liu <songliubraving@...com>
Cc: kbuild test robot <lkp@...el.com>,
David Miller <davem@...emloft.net>,
"kbuild-all@...org" <kbuild-all@...org>,
"alexei.starovoitov@...il.com" <alexei.starovoitov@...il.com>,
Martin Lau <kafai@...com>, Alexei Starovoitov <ast@...com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"liu.song.a23@...il.com" <liu.song.a23@...il.com>
Subject: Re: [PATCH net-next] tcp: add tracepoint trace_tcp_retransmit_synack()
On Thu, Oct 26, 2017 at 4:50 PM, Song Liu <songliubraving@...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?
>
> Any suggestions on how shall we proceed from here?
>
I think this warning is harmless, so perhaps not worthy time to
shut it up, unless sparse provides a simple way to do so.
Powered by blists - more mailing lists