From: David Miller <davem@davemloft.net>
To: parav@mellanox.com
Cc: netdev@vger.kernel.org, kuba@kernel.org, jiri@mellanox.com
Subject: Re: [PATCH net-next 0/4] devlink small improvements
Date: Tue, 21 Jul 2020 16:15:13 -0700 (PDT) [thread overview]
Message-ID: <20200721.161513.1845204518930431738.davem@davemloft.net> (raw)
In-Reply-To: <20200721165354.5244-1-parav@mellanox.com>
From: Parav Pandit <parav@mellanox.com>
Date: Tue, 21 Jul 2020 19:53:50 +0300
> This short series improves the devlink code for lock commment,
> simplifying checks and keeping the scope of mutex lock for necessary
> fields.
>
> Patch summary:
> Patch-1 Keep the devlink_mutex for only for necessary changes.
> Patch-2 Avoids duplicate check for reload flag
> Patch-3 Adds missing comment for the scope of devlink instance lock
> Patch-4 Constify devlink instance pointer
Series applied, thank you.
prev parent reply other threads:[~2020-07-21 23:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-21 16:53 [PATCH net-next 0/4] devlink small improvements Parav Pandit
2020-07-21 16:53 ` [PATCH net-next 1/4] devlink: Do not hold devlink mutex when initializing devlink fields Parav Pandit
2020-07-21 16:53 ` [PATCH net-next 2/4] devlink: Avoid duplicate check for reload enabled flag Parav Pandit
2020-07-21 16:53 ` [PATCH net-next 3/4] devlink: Add comment for devlink instance lock Parav Pandit
2020-07-21 16:53 ` [PATCH net-next 4/4] devlink: Constify devlink instance pointer Parav Pandit
2020-07-21 19:32 ` [PATCH net-next 0/4] devlink small improvements Jakub Kicinski
2020-07-21 23:15 ` David Miller [this message]
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=20200721.161513.1845204518930431738.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=jiri@mellanox.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=parav@mellanox.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).