From: Zi Shen Lim <zlim.lnx@gmail.com>
To: Daniel Borkmann <daniel@iogearbox.net>
Cc: kbuild test robot <lkp@intel.com>,
kbuild-all@01.org, "David S. Miller" <davem@davemloft.net>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will.deacon@arm.com>, Yang Shi <yang.shi@linaro.org>,
Alexei Starovoitov <ast@kernel.org>,
Network Development <netdev@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH net-next 1/3] arm64: bpf: implement bpf_tail_call() helper
Date: Mon, 6 Jun 2016 19:33:27 -0700 [thread overview]
Message-ID: <CAMDttNeURoDbn_Em=uV3PC68MwRqNbS0xEe7MAiii4H-eD5QFg@mail.gmail.com> (raw)
In-Reply-To: <5755302D.1000708@iogearbox.net>
On Mon, Jun 6, 2016 at 1:11 AM, Daniel Borkmann <daniel@iogearbox.net> wrote:
> On 06/06/2016 06:56 AM, Z Lim wrote:
> [...]
>>
>> How about the attached patch? Fixes compilation error on build
>> !CONFIG_BPF_SYSCALL.
>>
>> Also, should this patch be sent to net or net-next (along with this
>> series)?
>
>
> Looks good, feel free to add:
>
> Acked-by: Daniel Borkmann <daniel@iogearbox.net>
Thanks Daniel!
>
> I think net-next along with your series should be fine since the issue
> first appeared there. Thanks, Zi!
Sounds good. I'll include this as patch 1/4 (so it doesn't trip
kbuildbot) when I send out v2.
prev parent reply other threads:[~2016-06-07 2:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-04 22:00 [PATCH net-next 1/3] arm64: bpf: implement bpf_tail_call() helper Zi Shen Lim
2016-06-04 22:00 ` [PATCH net-next 2/3] arm64: bpf: optimize JMP_CALL Zi Shen Lim
2016-06-06 17:05 ` Will Deacon
2016-06-07 4:36 ` Z Lim
2016-06-07 8:10 ` Will Deacon
2016-06-04 22:00 ` [PATCH net-next 3/3] arm64: bpf: optimize LD_ABS, LD_IND Zi Shen Lim
2016-06-04 23:46 ` [PATCH net-next 1/3] arm64: bpf: implement bpf_tail_call() helper kbuild test robot
2016-06-05 7:53 ` Daniel Borkmann
2016-06-06 4:56 ` Z Lim
2016-06-06 8:11 ` Daniel Borkmann
2016-06-07 2:33 ` Zi Shen Lim [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='CAMDttNeURoDbn_Em=uV3PC68MwRqNbS0xEe7MAiii4H-eD5QFg@mail.gmail.com' \
--to=zlim.lnx@gmail.com \
--cc=ast@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=kbuild-all@01.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=netdev@vger.kernel.org \
--cc=will.deacon@arm.com \
--cc=yang.shi@linaro.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).