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 bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id CA448CDB474 for ; Fri, 13 Oct 2023 02:31:28 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:MIME-Version:References:In-Reply-To: Message-ID:Subject:Cc:To:From:Date:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=VLlroj9XHWY6OvkhADUfPiDx5XvwmHxB0rrd++5jjd4=; b=ABwLgmrICPcVdj YbvYlyoolYqZawDfWQF4+GxW6zs1Ya3WUEnv4LUrP5/+w+E4gXAxeTTwI2+DQ6+fT3iORAC1c0i++ KaSwi91rMTlQox0mSTUpkd1iI0UNFZUrSwZo/FaiI8/G86MenKCRMyeT72AfYLltI+syZp9Kwev54 S5hfYqVkp9WifR+ssEitUGLwyl6/MbsOP8qEPH6x3btZtk4GBxvjpa1om/JpLjp8yG3NWJktTFXg0 tqMVcTYLEOokAO3Bdbh+fGJKLQf8eCQvVPn4rD3O1bWlVhXe1NEy+gzM7g4HifGF31LnjAkPuddzU ABidEUFCmaTvIX75WSzQ==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.96 #2 (Red Hat Linux)) id 1qr7x8-002Iei-0k; Fri, 13 Oct 2023 02:31:02 +0000 Received: from mail-oo1-xc2a.google.com ([2607:f8b0:4864:20::c2a]) by bombadil.infradead.org with esmtps (Exim 4.96 #2 (Red Hat Linux)) id 1qr7x5-002Ie7-0y for linux-arm-kernel@lists.infradead.org; Fri, 13 Oct 2023 02:31:00 +0000 Received: by mail-oo1-xc2a.google.com with SMTP id 006d021491bc7-57bc2c2f13dso938311eaf.2 for ; Thu, 12 Oct 2023 19:30:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=networkplumber-org.20230601.gappssmtp.com; s=20230601; t=1697164257; x=1697769057; darn=lists.infradead.org; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:subject:cc:to:from:date:from:to:cc:subject:date :message-id:reply-to; bh=9AlSt/UmPpPe6qrtiCDOOfX5E4Znn3Anpv8O+XesUkY=; b=BbsXY/y1HIG80zuEO3z0tBHxDQjb1MOnMlw4Y/dByVekBESDbSFVgdLEm3kCbyBRUD 2o+Nkyokikk6hLMYqFE2fhqFtEwBzjiCV3SfxVstSZvzbLKqoa6roIf5pFjDTVRX83tO j3dGa0tJmZuXYWngEEGMKgh4GLb4UdW6826SoYY+XNvQju1KrFTcmcsE4qNMT8oc1mLS uDys1j2GomxqQjdwqooisxke9b4witdtuAa+SNNtgfZCsGwbl/LdG5rV8rqJ1smxgWFt KV64wpvcUoPW1jrONiXT3jqpwsMmGt/keKYDZkbYEPgemsomls+LhInpLAwPiZPv4zqh uERQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1697164257; x=1697769057; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:subject:cc:to:from:date:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=9AlSt/UmPpPe6qrtiCDOOfX5E4Znn3Anpv8O+XesUkY=; b=n9JXVX4g1xwF5TKL6u1CObx0t+Y9zuFpAGTcptgdoTp86swu9hQKX8tJIeIODYiwTK 8irW+V83mV6/sC8X4SzVcFO53j4w5Ntj7ETfHArup3xHnktAvMdKZGOptiMfQMByqvvh ACbRZz9oRO5h8zlufvyJyt8tCG4upnfGuyh8bCq7O7pUZS63NcXxyD10pP/Mv7aBKgek gowoKtRBusMQm5vrYdMHx4emjuUNXTa1I1YYjlzQ1h96JE6IwY9igv0OO7JzR3sqsIYm jWV8mHGSiUZZr8QjNXs/yBFAyPeNRR9nqtL2XAcZscvOiVBcGMuHWGmUe+K5gHbJoY+s 54AA== X-Gm-Message-State: AOJu0Yz/Htk0KScVnqRPcXXTeP8LUGvcLF7ijatdua2mkY1LIrF1Ob6J yjsoLB7fsRQbMVFh69M376dekA== X-Google-Smtp-Source: AGHT+IHH3S84jjyAAYr9ohOLASSdFKUdZmxPJl7BDa8RTAh3YuPi9ZQk+GpkCGTRwxLvo8btmJvx2g== X-Received: by 2002:a05:6358:9691:b0:164:8742:525 with SMTP id o17-20020a056358969100b0016487420525mr21597307rwa.17.1697164257258; Thu, 12 Oct 2023 19:30:57 -0700 (PDT) Received: from hermes.local (204-195-126-68.wavecable.com. [204.195.126.68]) by smtp.gmail.com with ESMTPSA id u204-20020a6279d5000000b006b1e8f17b85sm379297pfc.201.2023.10.12.19.30.56 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 12 Oct 2023 19:30:57 -0700 (PDT) Date: Thu, 12 Oct 2023 19:30:54 -0700 From: Stephen Hemminger To: Vladimir Oltean Cc: Florian Fainelli , netdev@vger.kernel.org, Andrew Lunn , Florian Fainelli , "David S. Miller" , Eric Dumazet , Jakub Kicinski , Paolo Abeni , Broadcom internal kernel review list , "open list:ARM/Mediatek SoC support" , "moderated list:ARM/Mediatek SoC support" Subject: Re: [PATCH net-next v2 2/2] net: dsa: Rename IFLA_DSA_MASTER to IFLA_DSA_CONDUIT Message-ID: <20231012193054.4c6759fe@hermes.local> In-Reply-To: <20231012231345.3thxxxhe7pxs5bib@skbuf> References: <20231011222026.4181654-1-florian.fainelli@broadcom.com> <20231011222026.4181654-3-florian.fainelli@broadcom.com> <20231011163003.32036b28@hermes.local> <20231012231345.3thxxxhe7pxs5bib@skbuf> MIME-Version: 1.0 X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20231012_193059_341502_179F2DA7 X-CRM114-Status: GOOD ( 14.60 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Fri, 13 Oct 2023 02:13:45 +0300 Vladimir Oltean wrote: > > I don't know if it would be acceptable in the kernel UAPI but what > > we did in DPDK for similar situation to cause warning on use of deprecated value. > > > > /** > > * Macro to mark macros and defines scheduled for removal > > */ > > #if defined(RTE_CC_GCC) || defined(RTE_CC_CLANG) > > #define RTE_PRAGMA(x) _Pragma(#x) > > #define RTE_PRAGMA_WARNING(w) RTE_PRAGMA(GCC warning #w) > > #define RTE_DEPRECATED(x) RTE_PRAGMA_WARNING(#x is deprecated) > > #else > > #define RTE_DEPRECATED(x) > > #endif > > > > ... > > #define RTE_DEV_WHITELISTED \ > > RTE_DEPRECATED(RTE_DEV_WHITELISTED) RTE_DEV_ALLOWED > > #define RTE_DEV_BLACKLISTED \ > > RTE_DEPRECATED(RTE_DEV_BLACKLISTED) RTE_DEV_BLOCKED > > What precedent exists in terms of intentionally breaking kernel headers? > If none, would this create one? It would cause warning, and most applications builds don't fail because of warning. Kernel already has __diag_warn macro which is similar, but see no usages of it. My comment was more of a "what if", probably not practical since it would just fuel lots of angry user feedback. _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel