From: Jakub Kicinski <kuba@kernel.org>
To: Roopa Prabhu <roopa@nvidia.com>
Cc: shshaikh@marvell.com, jdenham@redhat.com,
GR-Linux-NIC-Dev@marvell.com, manishc@marvell.com,
alexandre.belloni@bootlin.com, outreachy@lists.linux.dev,
netdev@vger.kernel.org, razor@blackwall.org,
bridge@lists.linux-foundation.org, jesse.brandeburg@intel.com,
linux-kernel@vger.kernel.org, vladimir.oltean@nxp.com,
sbrivio@redhat.com, claudiu.manoil@nxp.com,
anthony.l.nguyen@intel.com,
Alaa Mohamed <eng.alaamohamedsoliman.am@gmail.com>,
intel-wired-lan@lists.osuosl.org, pabeni@redhat.com,
davem@davemloft.net, UNGLinuxDriver@microchip.com
Subject: Re: [Bridge] [PATCH net-next v7 2/2] net: vxlan: Add extack support to vxlan_fdb_delete
Date: Thu, 12 May 2022 09:47:43 -0700 [thread overview]
Message-ID: <20220512094743.79f36d81@kernel.org> (raw)
In-Reply-To: <c5ec2677-3047-8a70-9769-d48a79703220@nvidia.com>
On Thu, 12 May 2022 09:22:17 -0700 Roopa Prabhu wrote:
> On 5/12/22 02:55, Alaa Mohamed wrote:
> > This patch adds extack msg support to vxlan_fdb_delete and vxlan_fdb_parse.
> > extack is used to propagate meaningful error msgs to the user of vxlan
> > fdb netlink api
> >
> > Signed-off-by: Alaa Mohamed <eng.alaamohamedsoliman.am@gmail.com>
Also the patches don't apply to net-next, again.
next prev parent reply other threads:[~2022-05-12 16:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-12 9:55 [Bridge] [PATCH net-next v7 0/2] propagate extack to vxlan_fdb_delete Alaa Mohamed
2022-05-12 9:55 ` [Bridge] [PATCH net-next v7 1/2] rtnetlink: add extack support in fdb del handlers Alaa Mohamed
2022-05-12 9:55 ` [Bridge] [PATCH net-next v7 2/2] net: vxlan: Add extack support to vxlan_fdb_delete Alaa Mohamed
2022-05-12 16:22 ` Roopa Prabhu
2022-05-12 16:47 ` Jakub Kicinski [this message]
2022-05-12 17:17 ` Roopa Prabhu
2022-05-12 17:50 ` Vladimir Oltean
2022-05-12 17:58 ` Jakub Kicinski
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=20220512094743.79f36d81@kernel.org \
--to=kuba@kernel.org \
--cc=GR-Linux-NIC-Dev@marvell.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=anthony.l.nguyen@intel.com \
--cc=bridge@lists.linux-foundation.org \
--cc=claudiu.manoil@nxp.com \
--cc=davem@davemloft.net \
--cc=eng.alaamohamedsoliman.am@gmail.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jdenham@redhat.com \
--cc=jesse.brandeburg@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=manishc@marvell.com \
--cc=netdev@vger.kernel.org \
--cc=outreachy@lists.linux.dev \
--cc=pabeni@redhat.com \
--cc=razor@blackwall.org \
--cc=roopa@nvidia.com \
--cc=sbrivio@redhat.com \
--cc=shshaikh@marvell.com \
--cc=vladimir.oltean@nxp.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).