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 56741C43334 for ; Tue, 5 Jul 2022 02:58:45 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234617AbiGEC6o (ORCPT ); Mon, 4 Jul 2022 22:58:44 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:41046 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S234636AbiGEC6n (ORCPT ); Mon, 4 Jul 2022 22:58:43 -0400 Received: from dfw.source.kernel.org (dfw.source.kernel.org [IPv6:2604:1380:4641:c500::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id CB2B1EA8 for ; Mon, 4 Jul 2022 19:58:41 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id 6A6F4617FF for ; Tue, 5 Jul 2022 02:58:41 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 81E4AC3411E; Tue, 5 Jul 2022 02:58:40 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1656989920; bh=BUfpGnRceY1qLcmHZTB4+k6pAmKzq7u3SN0qmg+6Sj0=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=lyY4Slfvoj3PCXFVIV8+h6wBKXHCZAPIxOg71vGittqbSqLSOGkGTsyoV/LowkT/w EMqu24IZI1O9parT486uU1RGXF2bJiwfQUIO46GNPcQRDDqFEIH1cVKQf6TsMFdTbI atGKP9GSFewOo+0BXQMSeu7dqGOh9mjEcfjfRMpQ9p/93QfC3ZuiLZCMgLteKFbyrW +sf9oF2XBNTUO+cRUbdkDNNy8/x2kfjL1yw9QNgivQfsNqzMJRxu7AdQtdPryfRdQx Ho21/VtvRp/gFkIBQlVlCRsItjxN7MpSDHuLrH66cz/lh7p8Oxx/mBoKErkROrFTd6 qXyVl5POZS4Bw== Date: Mon, 4 Jul 2022 19:58:39 -0700 From: Jakub Kicinski To: Jiri Pirko Cc: netdev@vger.kernel.org, davem@davemloft.net, pabeni@redhat.com, edumazet@google.com, mlxsw@nvidia.com, saeedm@nvidia.com, moshe@nvidia.com Subject: Re: [patch net-next 2/3] net: devlink: call lockdep_assert_held() for devlink->lock directly Message-ID: <20220704195839.34128dd3@kernel.org> In-Reply-To: References: <20220701095926.1191660-1-jiri@resnulli.us> <20220701095926.1191660-3-jiri@resnulli.us> <20220701093316.410157f3@kernel.org> <20220702122946.7bfc387a@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org On Mon, 4 Jul 2022 08:19:17 +0200 Jiri Pirko wrote: > Jakub, I don't really care. If you say we should do it differently, I > will do it differently. I just want the use to be consistent. From the > earlier reactions of DaveM on such helpers, I got an impression we don't > want them if possible. If this is no longer true, I'm fine with it. Just > tell me what I should do. As I said - my understanding is that we want to discourage (driver) authors from wrapping locks in lock/unlock helpers. Which was very fashionable at some point (IDK why, but it seem to have mostly gone away?). If the helper already exists I think consistency wins and we should use it.