From: Jiri Pirko <jiri@resnulli.us>
To: Vincent Mailhol <mailhol.vincent@wanadoo.fr>
Cc: Jiri Pirko <jiri@nvidia.com>,
netdev@vger.kernel.org, Jakub Kicinski <kuba@kernel.org>,
"David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
linux-kernel@vger.kernel.org,
Boris Brezillon <bbrezillon@kernel.org>,
Arnaud Ebalard <arno@natisbad.org>,
Srujana Challa <schalla@marvell.com>,
Kurt Kanzenbach <kurt@linutronix.de>,
Andrew Lunn <andrew@lunn.ch>,
Florian Fainelli <f.fainelli@gmail.com>,
Vladimir Oltean <olteanv@gmail.com>,
Michael Chan <michael.chan@broadcom.com>,
Ioana Ciornei <ioana.ciornei@nxp.com>,
Dimitris Michailidis <dmichail@fungible.com>,
Yisen Zhuang <yisen.zhuang@huawei.com>,
Salil Mehta <salil.mehta@huawei.com>,
Jesse Brandeburg <jesse.brandeburg@intel.com>,
Tony Nguyen <anthony.l.nguyen@intel.com>,
Sunil Goutham <sgoutham@marvell.com>,
Linu Cherian <lcherian@marvell.com>,
Geetha sowjanya <gakula@marvell.com>,
Jerin Jacob <jerinj@marvell.com>, hariprasad <hkelam@marvell.com>,
Subbaraya Sundeep <sbhatta@marvell.com>,
Taras Chornyi <tchornyi@marvell.com>,
Saeed Mahameed <saeedm@nvidia.com>,
Leon Romanovsky <leon@kernel.org>,
Ido Schimmel <idosch@nvidia.com>, Petr Machata <petrm@nvidia.com>,
Simon Horman <simon.horman@corigine.com>,
Shannon Nelson <snelson@pensando.io>,
drivers@pensando.io, Ariel Elior <aelior@marvell.com>,
Manish Chopra <manishc@marvell.com>,
Jonathan Lemon <jonathan.lemon@gmail.com>,
Vadim Fedorenko <vadfed@fb.com>,
Richard Cochran <richardcochran@gmail.com>,
Vadim Pasternak <vadimp@mellanox.com>,
Shalom Toledo <shalomt@mellanox.com>,
linux-crypto@vger.kernel.org, intel-wired-lan@lists.osuosl.org,
linux-rdma@vger.kernel.org, oss-drivers@corigine.com,
Jiri Pirko <jiri@mellanox.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
Hao Chen <chenhao288@hisilicon.com>,
Guangbin Huang <huangguangbin2@huawei.com>,
Minghao Chi <chi.minghao@zte.com.cn>,
Shijith Thotton <sthotton@marvell.com>
Subject: Re: [PATCH net-next v5 2/4] net: devlink: remove devlink_info_driver_name_put()
Date: Tue, 29 Nov 2022 09:25:46 +0100 [thread overview]
Message-ID: <Y4XCCl6F+N2w+ngn@nanopsycho> (raw)
In-Reply-To: <20221129000550.3833570-3-mailhol.vincent@wanadoo.fr>
Tue, Nov 29, 2022 at 01:05:48AM CET, mailhol.vincent@wanadoo.fr wrote:
>Now that the core sets the driver name attribute, drivers are not
>supposed to call devlink_info_driver_name_put() anymore. Remove it.
>
>Signed-off-by: Vincent Mailhol <mailhol.vincent@wanadoo.fr>
I agree with Jacob that this could be easily squashed to the previous
patch. One way or another:
Reviewed-by: Jiri Pirko <jiri@nvidia.com>
next prev parent reply other threads:[~2022-11-29 8:25 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-29 0:05 [PATCH net-next v5 0/4] net: devlink: return the driver name in devlink_nl_info_fill Vincent Mailhol
2022-11-29 0:05 ` [PATCH net-next v5 1/4] net: devlink: let the core report the driver name instead of the drivers Vincent Mailhol
2022-11-29 8:24 ` Jiri Pirko
2022-11-30 0:29 ` Vadim Fedorenko
2022-11-29 0:05 ` [PATCH net-next v5 2/4] net: devlink: remove devlink_info_driver_name_put() Vincent Mailhol
2022-11-29 0:23 ` Keller, Jacob E
2022-11-29 1:10 ` Vincent MAILHOL
2022-11-29 1:19 ` Keller, Jacob E
2022-11-29 8:25 ` Jiri Pirko [this message]
2022-11-29 9:37 ` Vincent MAILHOL
2022-11-29 16:23 ` Jakub Kicinski
2022-11-29 0:05 ` [PATCH net-next v5 3/4] net: devlink: make the devlink_ops::info_get() callback optional Vincent Mailhol
2022-11-29 0:24 ` [Intel-wired-lan] " Keller, Jacob E
2022-11-29 8:26 ` Jiri Pirko
2022-11-29 0:05 ` [PATCH net-next v5 4/4] net: devlink: clean-up empty devlink_ops::info_get() Vincent Mailhol
2022-11-29 8:27 ` Jiri Pirko
2022-11-29 0:25 ` [PATCH net-next v5 0/4] net: devlink: return the driver name in devlink_nl_info_fill Keller, Jacob E
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=Y4XCCl6F+N2w+ngn@nanopsycho \
--to=jiri@resnulli.us \
--cc=aelior@marvell.com \
--cc=andrew@lunn.ch \
--cc=anthony.l.nguyen@intel.com \
--cc=arno@natisbad.org \
--cc=bbrezillon@kernel.org \
--cc=chenhao288@hisilicon.com \
--cc=chi.minghao@zte.com.cn \
--cc=davem@davemloft.net \
--cc=dmichail@fungible.com \
--cc=drivers@pensando.io \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=gakula@marvell.com \
--cc=herbert@gondor.apana.org.au \
--cc=hkelam@marvell.com \
--cc=huangguangbin2@huawei.com \
--cc=idosch@nvidia.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=ioana.ciornei@nxp.com \
--cc=jerinj@marvell.com \
--cc=jesse.brandeburg@intel.com \
--cc=jiri@mellanox.com \
--cc=jiri@nvidia.com \
--cc=jonathan.lemon@gmail.com \
--cc=kuba@kernel.org \
--cc=kurt@linutronix.de \
--cc=lcherian@marvell.com \
--cc=leon@kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=mailhol.vincent@wanadoo.fr \
--cc=manishc@marvell.com \
--cc=michael.chan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=oss-drivers@corigine.com \
--cc=pabeni@redhat.com \
--cc=petrm@nvidia.com \
--cc=richardcochran@gmail.com \
--cc=saeedm@nvidia.com \
--cc=salil.mehta@huawei.com \
--cc=sbhatta@marvell.com \
--cc=schalla@marvell.com \
--cc=sgoutham@marvell.com \
--cc=shalomt@mellanox.com \
--cc=simon.horman@corigine.com \
--cc=snelson@pensando.io \
--cc=sthotton@marvell.com \
--cc=tchornyi@marvell.com \
--cc=vadfed@fb.com \
--cc=vadimp@mellanox.com \
--cc=yisen.zhuang@huawei.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).