From: Andy Shevchenko <andy@kernel.org>
To: Marcin Szycik <marcin.szycik@linux.intel.com>
Cc: jiri@resnulli.us, netdev@vger.kernel.org, idosch@nvidia.com,
jesse.brandeburg@intel.com, intel-wired-lan@lists.osuosl.org,
kuba@kernel.org, simon.horman@corigine.com, pabeni@redhat.com,
davem@davemloft.net
Subject: Re: [Intel-wired-lan] [PATCH iwl-next v3 6/6] ice: Add support for PFCP hardware offload in switchdev
Date: Mon, 24 Jul 2023 17:10:11 +0300 [thread overview]
Message-ID: <ZL6GQyy2x56+K9si@smile.fi.intel.com> (raw)
In-Reply-To: <24784f80-df7b-a666-a56b-9b4c288978a1@linux.intel.com>
On Mon, Jul 24, 2023 at 03:58:51PM +0200, Marcin Szycik wrote:
> On 21.07.2023 17:07, Andy Shevchenko wrote:
> > On Fri, Jul 21, 2023 at 09:15:32AM +0200, Marcin Szycik wrote:
...
> >> [1] https://lore.kernel.org/netdev/20230614091758.11180-1-marcin.szycik@linux.intel.com
> >
> > We have Link: tag for such kind of stuff.
>
> Are you sure this is a valid use of Link: tag?
Yes.
> Patch that is linked here is
> in another tree, and also I want to have [1] inline for context.
You can put it as
Link: $URI [1]
...
> >> #define ICE_TC_FLOWER_MASK_32 0xFFFFFFFF
> >
> > ...and (at least) this can utilize GENMASK().
>
> It can, but it's unrelated to this patch.
Right. Just a side note.
--
With Best Regards,
Andy Shevchenko
_______________________________________________
Intel-wired-lan mailing list
Intel-wired-lan@osuosl.org
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan
prev parent reply other threads:[~2023-07-24 15:24 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-21 7:15 [Intel-wired-lan] [PATCH iwl-next v3 0/6] ice: Add PFCP filter support Marcin Szycik
2023-07-21 7:15 ` [Intel-wired-lan] [PATCH iwl-next v3 1/6] ip_tunnel: use a separate struct to store tunnel params in the kernel Marcin Szycik
2023-07-21 14:21 ` Andy Shevchenko
2023-07-24 14:21 ` Alexander Lobakin
2023-07-21 7:15 ` [Intel-wired-lan] [PATCH iwl-next v3 2/6] ip_tunnel: convert __be16 tunnel flags to bitmaps Marcin Szycik
[not found] ` <ZLqZRFa1VOHHWCqX@smile.fi.intel.com>
2023-07-26 11:09 ` Alexander Lobakin
2023-07-26 12:01 ` Andy Shevchenko
2023-07-26 12:05 ` Andy Shevchenko
2023-07-26 13:16 ` Alexander Lobakin
2023-07-26 14:32 ` Andy Shevchenko
2023-07-21 7:15 ` [Intel-wired-lan] [PATCH iwl-next v3 3/6] pfcp: add PFCP module Marcin Szycik
2023-07-21 14:54 ` Andy Shevchenko
2023-07-24 10:36 ` Marcin Szycik
2023-07-21 7:15 ` [Intel-wired-lan] [PATCH iwl-next v3 4/6] pfcp: always set pfcp metadata Marcin Szycik
2023-07-21 15:02 ` Andy Shevchenko
2023-07-24 13:19 ` Marcin Szycik
2023-07-21 7:15 ` [Intel-wired-lan] [PATCH iwl-next v3 5/6] ice: refactor ICE_TC_FLWR_FIELD_ENC_OPTS Marcin Szycik
2023-07-21 7:15 ` [Intel-wired-lan] [PATCH iwl-next v3 6/6] ice: Add support for PFCP hardware offload in switchdev Marcin Szycik
2023-07-21 15:07 ` Andy Shevchenko
2023-07-24 13:58 ` Marcin Szycik
2023-07-24 14:10 ` Andy Shevchenko [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=ZL6GQyy2x56+K9si@smile.fi.intel.com \
--to=andy@kernel.org \
--cc=davem@davemloft.net \
--cc=idosch@nvidia.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jesse.brandeburg@intel.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=marcin.szycik@linux.intel.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=simon.horman@corigine.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