From: David Marchand <david.marchand@redhat.com>
To: Konstantin Ananyev <konstantin.v.ananyev@yandex.ru>
Cc: dev@dpdk.org, Konstantin Ananyev <konstantin.ananyev@huawei.com>
Subject: Re: [PATCH v2 0/3] fix bpf load hangs with six IPv6 addresses
Date: Thu, 4 Jul 2024 17:10:29 +0200 [thread overview]
Message-ID: <CAJFAV8y1HYx-niex4yhVc4dDx8=GkJ8cE9eNy6F2cuFn3GcF2g@mail.gmail.com> (raw)
In-Reply-To: <20240627180442.1602-1-konstantin.v.ananyev@yandex.ru>
On Thu, Jun 27, 2024 at 8:05 PM Konstantin Ananyev
<konstantin.v.ananyev@yandex.ru> wrote:
>
> From: Konstantin Ananyev <konstantin.ananyev@huawei.com>
>
> v2:
> - fix compilation warnings
> - fix nit in comments (Stephen)
>
> Konstantin Ananyev (3):
> bfp: fix MOV instruction evaluation
> bfp: fix load hangs with six IPv6 addresses
> test/bpf: add extra test cases for bpf convert
>
> app/test/test_bpf.c | 6 +
> lib/bpf/bpf_validate.c | 315 ++++++++++++++++++++++++++++++++++-------
> 2 files changed, 267 insertions(+), 54 deletions(-)
Series applied, thanks Konstantin.
--
David Marchand
prev parent reply other threads:[~2024-07-04 15:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-27 11:55 [PATCH " Konstantin Ananyev
2024-06-27 11:55 ` [PATCH 1/3] bfp: fix MOV instruction evaluation Konstantin Ananyev
2024-06-27 11:55 ` [PATCH 2/3] bfp: fix load hangs with six IPv6 addresses Konstantin Ananyev
2024-06-27 15:13 ` Stephen Hemminger
2024-06-27 11:55 ` [PATCH 3/3] test/bpf: add extra test cases for bpf convert Konstantin Ananyev
2024-06-27 15:15 ` Stephen Hemminger
2024-06-27 12:41 ` [PATCH 0/3] fix bpf load hangs with six IPv6 addresses Morten Brørup
2024-06-27 18:04 ` [PATCH v2 " Konstantin Ananyev
2024-06-27 18:04 ` [PATCH v2 1/3] bfp: fix MOV instruction evaluation Konstantin Ananyev
2024-06-27 18:04 ` [PATCH v2 2/3] bfp: fix load hangs with six IPv6 addresses Konstantin Ananyev
2024-06-27 18:04 ` [PATCH v2 3/3] test/bpf: add extra test cases for bpf convert Konstantin Ananyev
2024-07-04 15:10 ` David Marchand [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='CAJFAV8y1HYx-niex4yhVc4dDx8=GkJ8cE9eNy6F2cuFn3GcF2g@mail.gmail.com' \
--to=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=konstantin.ananyev@huawei.com \
--cc=konstantin.v.ananyev@yandex.ru \
/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).