From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 48FE0C433EF for ; Tue, 15 Mar 2022 08:31:15 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1345998AbiCOIcX (ORCPT ); Tue, 15 Mar 2022 04:32:23 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:54964 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1345969AbiCOIcT (ORCPT ); Tue, 15 Mar 2022 04:32:19 -0400 Received: from wout1-smtp.messagingengine.com (wout1-smtp.messagingengine.com [64.147.123.24]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 7F2CD4C787 for ; Tue, 15 Mar 2022 01:31:02 -0700 (PDT) Received: from compute2.internal (compute2.nyi.internal [10.202.2.46]) by mailout.west.internal (Postfix) with ESMTP id 73572320157F; Tue, 15 Mar 2022 04:31:01 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute2.internal (MEProxy); Tue, 15 Mar 2022 04:31:02 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-type:date:date:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=a09louK9PNjhrPgEA TZn3aIMtSVDu31QXYfPMVgzL9M=; b=DFYSaDs+9YjmYiHBvA0b8R1zmJbVtOqiv K1ezOTQFornDqRFexmfIg7MB90mDzNJt5bLzqlZCwC5FboKlPRyhTtO1+A3Nu8Z9 uyY3S9/AqMZUmd/Mh5ZV4ykONjrX07xs88H4bYLF2f/UpGBbC2JhyIN8as+rhJEt hBGsw5DbTIKOesjSxbNZ+iZ+pGYhl4J7sEU4YJO+57vTnDO/NiK2PUy1wpxSmmwE nLGJDEVEpYtm9W2LDbCl5bzWWfXbNxB+xweRw/JqsA3LrgxiyqhBJHiFRMw3b8so cJDMKtfskIYxXdItsxhTmivv/VJS1LxGAldevZupJJLo1Z74VNzzw== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvvddruddvledguddulecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecunecujfgurhepfffhvffukfhfgggtuggjsehttd ertddttddvnecuhfhrohhmpefkughoucfutghhihhmmhgvlhcuoehiughoshgthhesihgu ohhstghhrdhorhhgqeenucggtffrrghtthgvrhhnpedtffekkeefudffveegueejffejhf etgfeuuefgvedtieehudeuueekhfduheelteenucevlhhushhtvghrufhiiigvpedtnecu rfgrrhgrmhepmhgrihhlfhhrohhmpehiughoshgthhesihguohhstghhrdhorhhg X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Tue, 15 Mar 2022 04:31:00 -0400 (EDT) Date: Tue, 15 Mar 2022 10:30:57 +0200 From: Ido Schimmel To: Jakub Kicinski Cc: davem@davemloft.net, netdev@vger.kernel.org, jiri@nvidia.com, idosch@nvidia.com, petrm@nvidia.com, simon.horman@corigine.com, louis.peens@corigine.com, leon@kernel.org Subject: Re: [PATCH net-next 5/6] devlink: hold the instance lock in port_split / port_unsplit callbacks Message-ID: References: <20220315060009.1028519-1-kuba@kernel.org> <20220315060009.1028519-6-kuba@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20220315060009.1028519-6-kuba@kernel.org> Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org On Mon, Mar 14, 2022 at 11:00:08PM -0700, Jakub Kicinski wrote: > Let the core take the devlink instance lock around port splitting > and remove the now redundant locking in the drivers. > > Signed-off-by: Jakub Kicinski Reviewed-by: Ido Schimmel Tested-by: Ido Schimmel