From: patchwork-bot+netdevbpf@kernel.org
To: Maksym Glubokiy <maksym.glubokiy@plvision.eu>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, jhs@mojatatu.com, xiyou.wangcong@gmail.com,
jiri@resnulli.us, louis.peens@corigine.com, elic@nvidia.com,
simon.horman@corigine.com, baowen.zheng@corigine.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v2 0/2] net: prestera: add support for port range filters
Date: Wed, 13 Jul 2022 12:00:14 +0000 [thread overview]
Message-ID: <165771361432.14728.4361651412076279677.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220711150908.1030650-1-maksym.glubokiy@plvision.eu>
Hello:
This series was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:
On Mon, 11 Jul 2022 18:09:06 +0300 you wrote:
> This adds support for port-range rules in Marvel Prestera driver:
>
> $ tc qdisc add ... clsact
> $ tc filter add ... flower ... src_port <PMIN>-<PMAX> ...
>
> Maksym Glubokiy (2):
> net: extract port range fields from fl_flow_key
> net: prestera: add support for port range filters
>
> [...]
Here is the summary with links:
- [net-next,v2,1/2] net: extract port range fields from fl_flow_key
https://git.kernel.org/netdev/net-next/c/83d85bb06915
- [net-next,v2,2/2] net: prestera: add support for port range filters
https://git.kernel.org/netdev/net-next/c/551871bfc82c
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2022-07-13 12:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-11 15:09 Maksym Glubokiy
2022-07-11 15:09 ` [PATCH net-next v2 1/2] net: extract port range fields from fl_flow_key Maksym Glubokiy
2022-07-11 15:09 ` [PATCH net-next v2 2/2] net: prestera: add support for port range filters Maksym Glubokiy
2022-07-13 12:00 ` patchwork-bot+netdevbpf [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=165771361432.14728.4361651412076279677.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=baowen.zheng@corigine.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=elic@nvidia.com \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=louis.peens@corigine.com \
--cc=maksym.glubokiy@plvision.eu \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=simon.horman@corigine.com \
--cc=xiyou.wangcong@gmail.com \
/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
all inboxes | Powered by JetHome®