From: Tony Nguyen <anthony.l.nguyen@intel.com>
To: "Drewek, Wojciech" <wojciech.drewek@intel.com>,
Vladimir Oltean <vladimir.oltean@nxp.com>,
Jakub Kicinski <kuba@kernel.org>
Cc: Jiri Pirko <jiri@resnulli.us>, Ido Schimmel <idosch@idosch.org>,
"Vlad Buslov" <vladbu@nvidia.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
Simon Horman <horms@kernel.org>,
"Buvaneswaran, Sujai" <sujai.buvaneswaran@intel.com>
Subject: Re: [PATCH net-next 2/7] ice: Support untagged VLAN traffic in br offload
Date: Fri, 4 Aug 2023 11:02:26 -0700 [thread overview]
Message-ID: <cffa2e0b-bd03-7f12-014c-c6830fd43917@intel.com> (raw)
In-Reply-To: <MW4PR11MB577606B881AAF52B44B76839FD09A@MW4PR11MB5776.namprd11.prod.outlook.com>
On 8/4/2023 2:32 AM, Drewek, Wojciech wrote:
> Thanks for clarification Vladimir, we will change our implementation.
> Tony, you can drop this patch from the pull request.
Will do.
Thanks,
Tony
next prev parent reply other threads:[~2023-08-04 18:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-01 17:31 [PATCH net-next 0/7][pull request] Intel Wired LAN Driver Updates 2023-08-01 (ice) Tony Nguyen
2023-08-01 17:31 ` [PATCH net-next 1/7] ice: Accept LAG netdevs in bridge offloads Tony Nguyen
2023-08-01 17:31 ` [PATCH net-next 2/7] ice: Support untagged VLAN traffic in br offload Tony Nguyen
2023-08-03 2:31 ` Jakub Kicinski
2023-08-03 15:58 ` Vladimir Oltean
2023-08-04 9:32 ` Drewek, Wojciech
2023-08-04 18:02 ` Tony Nguyen [this message]
2023-08-01 17:31 ` [PATCH net-next 3/7] ice: Add direction metadata Tony Nguyen
2023-08-01 17:31 ` [PATCH net-next 4/7] ice: Rename enum ice_pkt_flags values Tony Nguyen
2023-08-01 17:31 ` [PATCH net-next 5/7] ice: Add get C827 PHY index function Tony Nguyen
2023-08-03 2:28 ` Jakub Kicinski
2023-08-01 17:31 ` [PATCH net-next 6/7] ice: add FW load wait Tony Nguyen
2023-08-01 17:31 ` [PATCH net-next 7/7] ice: clean up __ice_aq_get_set_rss_lut() Tony Nguyen
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=cffa2e0b-bd03-7f12-014c-c6830fd43917@intel.com \
--to=anthony.l.nguyen@intel.com \
--cc=horms@kernel.org \
--cc=idosch@idosch.org \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sujai.buvaneswaran@intel.com \
--cc=vladbu@nvidia.com \
--cc=vladimir.oltean@nxp.com \
--cc=wojciech.drewek@intel.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;
as well as URLs for NNTP newsgroup(s).