From: Alexei Starovoitov <ast@plumgrid•com>
To: David Miller <davem@davemloft•net>
Cc: holzheu@linux•vnet.ibm.com, schwidefsky@de•ibm.com,
heiko.carstens@de•ibm.com, daniel@iogearbox•net,
netdev@vger•kernel.org
Subject: Re: [PATCH net-next 0/3] s390/bpf: implement bpf_tail_call JIT support
Date: Mon, 01 Jun 2015 22:50:56 -0700 [thread overview]
Message-ID: <556D4440.5010503@plumgrid.com> (raw)
In-Reply-To: <20150531.213931.282168647572228489.davem@davemloft.net>
On 5/31/15 9:39 PM, David Miller wrote:
> From: Alexei Starovoitov <ast@plumgrid•com>
> Date: Sat, 30 May 2015 10:42:08 -0700
>
>> This set is for net-next tree.
>>
>> Patch 3 adds bpf_tail_call() support for s390x JIT. It has
>> a dependency on patches 1 and 2 that will also be submitted
>> to stable via Martin Schwidefsky.
>
> In this kind of scenerio, patches #1 and #2 should go via my
> tree (somehow), and then when I next merge 'net' into 'net-next'
> you can submit patch #3.
all makes sense. Just resubmitted #1 and #2 against 'net' with
proper 'Fixes' tag.
prev parent reply other threads:[~2015-06-02 5:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-30 17:42 [PATCH net-next 0/3] s390/bpf: implement bpf_tail_call JIT support Alexei Starovoitov
2015-05-30 17:42 ` [PATCH net-next 1/3] s390/bpf: fix stack allocation Alexei Starovoitov
2015-05-30 17:42 ` [PATCH net-next 2/3] s390/bpf: fix bpf frame pointer setup Alexei Starovoitov
2015-05-30 17:42 ` [PATCH net-next 3/3] s390/bpf: implement bpf_tail_call() helper Alexei Starovoitov
2015-06-01 4:39 ` [PATCH net-next 0/3] s390/bpf: implement bpf_tail_call JIT support David Miller
2015-06-02 5:50 ` Alexei Starovoitov [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=556D4440.5010503@plumgrid.com \
--to=ast@plumgrid$(echo .)com \
--cc=daniel@iogearbox$(echo .)net \
--cc=davem@davemloft$(echo .)net \
--cc=heiko.carstens@de$(echo .)ibm.com \
--cc=holzheu@linux$(echo .)vnet.ibm.com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=schwidefsky@de$(echo .)ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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