From: David Miller <davem@davemloft.net>
To: idosch@mellanox.com
Cc: netdev@vger.kernel.org, jiri@mellanox.com, mlxsw@mellanox.com
Subject: Re: [PATCH net 0/2] mlxsw: Couple of fixes
Date: Thu, 04 Oct 2018 09:56:54 -0700 (PDT) [thread overview]
Message-ID: <20181004.095654.479915005653032063.davem@davemloft.net> (raw)
In-Reply-To: <20181004154728.8054-1-idosch@mellanox.com>
From: Ido Schimmel <idosch@mellanox.com>
Date: Thu, 4 Oct 2018 15:48:00 +0000
> First patch works around an hardware issue in Spectrum-2 where a field
> indicating the event type is always set to the same value. Since there
> are only two event types and they are reported using different queues,
> we can use the queue number to derive the event type.
>
> Second patch prevents a router interface (RIF) leakage when a VLAN
> device is deleted from on top a bridge device.
Series applied, and patch #2 queued up for -stable.
I was thinking about Fixes tags for the situation in patch #2 a bit,
and it's probably best to list two Fixes tags. One for the original
bug that wasn't fixed properly, and one for the incomplete fix.
It's nice that you mentioned the incomplete fix in the commit message
but a backporter might miss this chain of commits and dependencies it
if it isn't in the Fixes: tags.
Thanks.
next prev parent reply other threads:[~2018-10-04 23:59 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-04 15:48 [PATCH net 0/2] mlxsw: Couple of fixes Ido Schimmel
2018-10-04 15:48 ` [PATCH net 1/2] mlxsw: pci: Derive event type from event queue number Ido Schimmel
2018-10-04 15:48 ` [PATCH net 2/2] mlxsw: spectrum: Delete RIF when VLAN device is removed Ido Schimmel
2018-10-04 16:56 ` David Miller [this message]
2018-10-04 17:05 ` [PATCH net 0/2] mlxsw: Couple of fixes Ido Schimmel
-- strict thread matches above, loose matches on Subject: below --
2020-11-17 17:33 Ido Schimmel
2020-11-18 19:09 ` Jakub Kicinski
2019-12-29 11:40 Ido Schimmel
2019-12-29 20:30 ` David Miller
2018-10-29 14:26 Ido Schimmel
2018-10-30 3:48 ` David Miller
2018-02-27 11:56 [patch net 0/2] mlxsw: couple " Jiri Pirko
2018-02-27 19:39 ` David Miller
2018-02-28 7:09 ` Jiri Pirko
2018-01-10 10:42 Jiri Pirko
2018-01-10 20:58 ` David Miller
2017-08-04 12:12 [patch net 0/2] mlxsw: Couple " Jiri Pirko
2017-08-04 18:17 ` David Miller
2017-05-18 7:18 [patch net 0/2] mlxsw: couple " Jiri Pirko
2017-05-18 15:05 ` David Miller
2017-03-14 12:59 [patch net 0/2] mlxsw: Couple " Jiri Pirko
2017-03-14 18:35 ` David Miller
2016-11-11 10:20 Jiri Pirko
2016-11-13 17:48 ` David Miller
2016-10-25 9:25 Jiri Pirko
2016-10-28 17:44 ` David Miller
2016-10-04 7:46 Jiri Pirko
2016-10-05 0:29 ` David Miller
2016-10-05 11:14 ` Jiri Pirko
2016-09-08 6:16 [patch net 0/2] mlxsw: couple " Jiri Pirko
2016-09-09 23:57 ` David Miller
2016-08-24 9:18 Jiri Pirko
2016-08-24 16:39 ` David Miller
2016-06-17 13:09 Jiri Pirko
2016-06-18 4:58 ` David Miller
2016-06-09 7:51 Jiri Pirko
2016-06-09 18:21 ` David Miller
2016-05-06 20:18 [patch net 0/2] mlxsw: Couple " Jiri Pirko
2016-05-06 22:33 ` David Miller
2016-03-07 8:24 [patch net 0/2] mlxsw: couple " Jiri Pirko
2015-10-08 13:17 Jiri Pirko
2015-10-11 12:08 ` David Miller
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=20181004.095654.479915005653032063.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=idosch@mellanox.com \
--cc=jiri@mellanox.com \
--cc=mlxsw@mellanox.com \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).