From: Saeed Mahameed <saeed@kernel.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Saeed Mahameed <saeedm@mellanox.com>
Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org,
netdev@vger.kernel.org, Roi Dayan <roid@mellanox.com>
Subject: Re: [PATCH 4.19] net/mlx5e: Don't support phys switch id if not in switchdev mode
Date: Thu, 10 Sep 2020 11:46:36 -0700 [thread overview]
Message-ID: <fc4effe1bbe6e9c68f4bdd863e3d38cbab52a285.camel@kernel.org> (raw)
In-Reply-To: <20200807131323.GA664450@kroah.com>
On Fri, 2020-08-07 at 15:13 +0200, Greg Kroah-Hartman wrote:
> On Thu, Aug 06, 2020 at 07:05:42PM -0700, Saeed Mahameed wrote:
> > From: Roi Dayan <roid@mellanox.com>
> >
> > Support for phys switch id ndo added for representors and if
> > we do not have representors there is no need to support it.
> > Since each port return different switch id supporting this
> > block support for creating bond over PFs and attaching to bridge
> > in legacy mode.
> >
> > This bug doesn't exist upstream as the code got refactored and the
> > netdev api is totally different.
> >
> > Fixes: cb67b832921c ("net/mlx5e: Introduce SRIOV VF representors")
> > Signed-off-by: Roi Dayan <roid@mellanox.com>
> > Signed-off-by: Saeed Mahameed <saeedm@mellanox.com>
> > ---
> > Hi Greg,
> >
> > Sorry for submitting a non upstream patch, but this bug is
> > bothering some users on 4.19-stable kernels and it doesn't exist
> > upstream, so i hope you are ok with backporting this one liner
> > patch.
>
> Also queued up to 4.9.y and 4.14.y.
>
Hi Greg, the request was originally made for 4.19.y kernel,
I see the patch in 4.9 and 4.14 but not in 4.19 can we push it to 4.19
as well ?
Thanks,
Saeed.
next prev parent reply other threads:[~2020-09-10 18:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-07 2:05 [PATCH 4.19] net/mlx5e: Don't support phys switch id if not in switchdev mode Saeed Mahameed
2020-08-07 13:13 ` Greg Kroah-Hartman
2020-09-10 18:46 ` Saeed Mahameed [this message]
2020-09-11 11:57 ` Greg Kroah-Hartman
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=fc4effe1bbe6e9c68f4bdd863e3d38cbab52a285.camel@kernel.org \
--to=saeed@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=roid@mellanox.com \
--cc=saeedm@mellanox.com \
--cc=stable@vger.kernel.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