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 23E72C433EF for ; Fri, 15 Jul 2022 19:58:11 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229828AbiGOT6J (ORCPT ); Fri, 15 Jul 2022 15:58:09 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:57084 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229648AbiGOT6I (ORCPT ); Fri, 15 Jul 2022 15:58:08 -0400 Received: from mga11.intel.com (mga11.intel.com [192.55.52.93]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 8145613F76; Fri, 15 Jul 2022 12:58:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1657915087; x=1689451087; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=ehY6mVr5usI1pbUCrRe9NIpChbrEMhuIPu5cO3R+A8k=; b=STj236lGwgtGWu2u0vYygVwG0M16d+xfHiCb+j2pkab0/v5eD1X8QwR+ XJCa0G/8syP2Xs1WeH6JMnARBpu7BkqHNeQeDGR2f++Hbqg9l2+lpr/5x B9buEVdQeLf12pNlOmWJuJt/rdA0mB4PYHAFsJAoiounJn/AhMDX7NAKy VAXMCwiL0MW9TbNdR3Z1St/HWRdnvE+rP0PWS94snFyvLV3F6y0ctauU6 jX2repe5re74YqS1mc1cFGRAV3Ts1lFFbWUjBHJU0dufoTPaXECYRJbGa DA+cWyelRHuIuuypFEK72lSjeNGWGTl16VBPdMHiPG8dcLkrbrTbpfo2m A==; X-IronPort-AV: E=McAfee;i="6400,9594,10409"; a="283447205" X-IronPort-AV: E=Sophos;i="5.92,274,1650956400"; d="scan'208";a="283447205" Received: from fmsmga006.fm.intel.com ([10.253.24.20]) by fmsmga102.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 15 Jul 2022 12:58:07 -0700 X-IronPort-AV: E=Sophos;i="5.92,274,1650956400"; d="scan'208";a="842634224" Received: from smile.fi.intel.com ([10.237.72.54]) by fmsmga006-auth.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 15 Jul 2022 12:58:00 -0700 Received: from andy by smile.fi.intel.com with local (Exim 4.96) (envelope-from ) id 1oCRRk-001JE8-0C; Fri, 15 Jul 2022 22:57:56 +0300 Date: Fri, 15 Jul 2022 22:57:55 +0300 From: Andy Shevchenko To: Russell King Cc: Andrew Lunn , Heiner Kallweit , Alexandre Belloni , Alvin __ipraga , Claudiu Manoil , Daniel Scally , "David S. Miller" , DENG Qingfang , Eric Dumazet , Florian Fainelli , George McCollister , Greg Kroah-Hartman , Hauke Mehrtens , Heikki Krogerus , Jakub Kicinski , Kurt Kanzenbach , Landen Chao , Linus Walleij , linux-acpi@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-mediatek@lists.infradead.org, Matthias Brugger , netdev@vger.kernel.org, Paolo Abeni , "Rafael J. Wysocki" , Sakari Ailus , Sean Wang , UNGLinuxDriver@microchip.com, Vivien Didelot , Vladimir Oltean , Woojung Huh , Marek =?iso-8859-1?Q?Beh=FAn?= Subject: Re: [PATCH net-next 2/6] software node: allow named software node to be created Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org On Fri, Jul 15, 2022 at 05:01:32PM +0100, Russell King wrote: > From: Vladimir Oltean > > Allow a named software node to be created, which is needed for software > nodes for a fixed-link specification for DSA. In general I have no objection, but what's worrying me is a possibility to collide in namespace. With the current code the name is generated based on unique IDs, how can we make this one more robust? -- With Best Regards, Andy Shevchenko