From: Marcin Szycik <marcin.szycik@linux.intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [PATCH net-next v9 0/7] ice: GTP support in switchdev
Date: Fri, 25 Feb 2022 12:48:01 +0100 [thread overview]
Message-ID: <f11878c1-2486-b777-9701-912b048e5f0e@linux.intel.com> (raw)
In-Reply-To: <YhgKO8rdxMxclZPm@nataraja>
Hi Harald,
Thank you for reviewing the gtp part!
On 24-Feb-22 23:44, Harald Welte wrote:
> Hi Marcin,
>
> On Thu, Feb 24, 2022 at 07:54:53PM +0100, Marcin Szycik wrote:
>> Add support for adding GTP-C and GTP-U filters in switchdev mode.
>
> For the changes to the gtp.ko driver this v9 looks fine to me. I cannot
> comment about the switchdevs bits, those are beyond my expertise.
>
> Regards,
> Harald
prev parent reply other threads:[~2022-02-25 11:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-24 18:54 [Intel-wired-lan] [PATCH net-next v9 0/7] ice: GTP support in switchdev Marcin Szycik
2022-02-24 18:54 ` [Intel-wired-lan] [PATCH net-next v9 1/7] gtp: Allow to create GTP device without FDs Marcin Szycik
2022-02-24 18:54 ` [Intel-wired-lan] [PATCH net-next v9 2/7] gtp: Implement GTP echo response Marcin Szycik
2022-02-24 18:54 ` [Intel-wired-lan] [PATCH net-next v9 3/7] gtp: Implement GTP echo request Marcin Szycik
2022-02-24 22:42 ` Harald Welte
2022-02-24 18:54 ` [Intel-wired-lan] [PATCH net-next v9 4/7] net/sched: Allow flower to match on GTP options Marcin Szycik
2022-02-24 18:54 ` [Intel-wired-lan] [PATCH net-next v9 5/7] gtp: Add support for checking GTP device type Marcin Szycik
2022-02-24 18:54 ` [Intel-wired-lan] [PATCH net-next v9 6/7] ice: Fix FV offset searching Marcin Szycik
2022-02-24 18:55 ` [Intel-wired-lan] [PATCH net-next v9 7/7] ice: Support GTP-U and GTP-C offload in switchdev Marcin Szycik
2022-02-24 22:44 ` [Intel-wired-lan] [PATCH net-next v9 0/7] ice: GTP support " Harald Welte
2022-02-25 11:48 ` Marcin Szycik [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=f11878c1-2486-b777-9701-912b048e5f0e@linux.intel.com \
--to=marcin.szycik@linux.intel.com \
--cc=intel-wired-lan@osuosl.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