From: valdis.kletnieks@vt.edu
To: Daniel Borkmann <daniel@iogearbox.net>
Cc: Song Liu <liu.song.a23@gmail.com>,
Alexei Starovoitov <ast@kernel.org>,
Networking <netdev@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] bpf/core.c - silence warning messages
Date: Mon, 28 Jan 2019 18:48:13 -0500 [thread overview]
Message-ID: <10399.1548719293@turing-police.cc.vt.edu> (raw)
In-Reply-To: <3c8c866f-c665-ff82-a0ab-a4eafd28b20f@iogearbox.net>
On Tue, 29 Jan 2019 00:22:26 +0100, Daniel Borkmann said:
> I think moving in separate file would be overkill, imho. However, lets get
> the kdoc and prototype warning fixed.
I have a bunch of spare time at the moment, so the kdoc and prototype
warnings are on my to-do list.
next prev parent reply other threads:[~2019-01-28 23:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-28 4:11 [PATCH] bpf/core.c - silence warning messages valdis.kletnieks
2019-01-28 17:18 ` Song Liu
2019-01-28 23:22 ` Daniel Borkmann
2019-01-28 23:48 ` valdis.kletnieks [this message]
2019-01-28 23:54 ` Daniel Borkmann
2019-01-28 23:35 ` valdis.kletnieks
2019-01-29 3:12 ` Song Liu
-- strict thread matches above, loose matches on Subject: below --
2019-06-07 2:39 Valdis Klētnieks
2019-06-11 5:46 ` Andrii Nakryiko
2019-06-12 14:56 ` 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=10399.1548719293@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=ast@kernel.org \
--cc=daniel@iogearbox.net \
--cc=linux-kernel@vger.kernel.org \
--cc=liu.song.a23@gmail.com \
--cc=netdev@vger.kernel.org \
/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