Netdev Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Parav Pandit <parav@nvidia.com>
To: Jakub Kicinski <kuba@kernel.org>, Parav Pandit <parav@mellanox.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"davem@davemloft.net" <davem@davemloft.net>
Subject: RE: [PATCH net-next 0/2] devlink fixes for port and reporter field access
Date: Tue, 25 Aug 2020 20:10:53 +0000	[thread overview]
Message-ID: <BY5PR12MB4322A9BE54C02185FECFAE6FDC570@BY5PR12MB4322.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20200824134846.6125c838@kicinski-fedora-PC1C0HJN>


> From: netdev-owner@vger.kernel.org <netdev-owner@vger.kernel.org>
> On Behalf Of Jakub Kicinski
> 
> On Fri, 21 Aug 2020 22:12:19 +0300 Parav Pandit wrote:
> > From: Parav Pandit <parav@nvidia.com>
> >
> > Hi Dave,
> >
> > These series contains two small fixes of devlink.
> >
> > Patch-1 initializes port reporter fields early enough to avoid access
> > before initialized error.
> > Patch-2 protects port list lock during traversal.
> 
> Reviewed-by: Jakub Kicinski <kuba@kernel.org>
> 
> Why did you tag this for net-next, instead of net?
My bad. I will take care for subsequent fixes to tag for net.

  reply	other threads:[~2020-08-25 20:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-21 19:12 Parav Pandit
2020-08-21 19:12 ` [PATCH net-next 1/2] devlink: Fix per port reporter fields initialization Parav Pandit
2020-08-21 19:12 ` [PATCH net-next 2/2] devlink: Protect devlink port list traversal Parav Pandit
2020-08-24 20:48 ` [PATCH net-next 0/2] devlink fixes for port and reporter field access Jakub Kicinski
2020-08-25 20:10   ` Parav Pandit [this message]
2020-08-24 23:03 ` 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=BY5PR12MB4322A9BE54C02185FECFAE6FDC570@BY5PR12MB4322.namprd12.prod.outlook.com \
    --to=parav@nvidia.com \
    --cc=davem@davemloft.net \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=parav@mellanox.com \
    --subject='RE: [PATCH net-next 0/2] devlink fixes for port and reporter field access' \
    /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

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).