From: Jesper Dangaard Brouer <brouer@redhat.com>
To: kbuild test robot <lkp@intel.com>
Cc: kbuild-all@01.org, netdev@vger.kernel.org,
Daniel Borkmann <borkmann@iogearbox.net>,
Alexei Starovoitov <alexei.starovoitov@gmail.com>,
brouer@redhat.com
Subject: Re: [bpf-next PATCH 3/3] xdp: split code for map vs non-map redirect
Date: Tue, 4 Sep 2018 18:57:59 +0200 [thread overview]
Message-ID: <20180904185759.6d940bfa@redhat.com> (raw)
In-Reply-To: <20180904153945.GZ17047@intel.com>
On Tue, 4 Sep 2018 23:39:45 +0800
kbuild test robot <lkp@intel.com> wrote:
> Hi Jesper,
>
> Thank you for the patch! Perhaps something to improve:
Daniel is faster than kbuild test-robot, and have already pointed this
out, and it should be fixed in V2.
--
Best regards,
Jesper Dangaard Brouer
MSc.CS, Principal Kernel Engineer at Red Hat
LinkedIn: http://www.linkedin.com/in/brouer
prev parent reply other threads:[~2018-09-04 21:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-31 15:26 [bpf-next PATCH 0/3] XDP micro optimizations for redirect Jesper Dangaard Brouer
2018-08-31 15:26 ` [bpf-next PATCH 1/3] xdp: unlikely instrumentation for xdp map redirect Jesper Dangaard Brouer
2018-08-31 15:26 ` [bpf-next PATCH 2/3] xdp: explicit inline __xdp_map_lookup_elem Jesper Dangaard Brouer
2018-08-31 15:26 ` [bpf-next PATCH 3/3] xdp: split code for map vs non-map redirect Jesper Dangaard Brouer
2018-08-31 18:37 ` Daniel Borkmann
2018-09-04 15:39 ` [RFC PATCH] xdp: xdp_do_redirect_slow() can be static kbuild test robot
2018-09-04 15:39 ` [bpf-next PATCH 3/3] xdp: split code for map vs non-map redirect kbuild test robot
2018-09-04 16:57 ` Jesper Dangaard Brouer [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=20180904185759.6d940bfa@redhat.com \
--to=brouer@redhat.com \
--cc=alexei.starovoitov@gmail.com \
--cc=borkmann@iogearbox.net \
--cc=kbuild-all@01.org \
--cc=lkp@intel.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;
as well as URLs for NNTP newsgroup(s).