From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 4B8F1191F74 for ; Fri, 25 Apr 2025 17:51:46 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1745603507; cv=none; b=jRJfZdCGCKl9Xfw3QgiL6bMhBWxC/N+UgXn3qXeoYr3q38YtALJifBzc+b2HiuIC4Rr4hTKFwFuzHX7Px8pZseYha48w0Adfme5VH3caYBuqDE9kN6+VruahiRG6zuKxZCnOGbHE13lRDe4W0gf5KApS4ySuGHFj0XaH3TCrTF8= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1745603507; c=relaxed/simple; bh=fpT/qX457YU2Zza6G3iWC4fjaELLorRrFMo5HBGKfiY=; h=Date:From:To:Cc:Subject:Message-ID:In-Reply-To:References: MIME-Version:Content-Type; b=PFfhZijv2Q1oVFEEy40r/HMhpI/pbFVItRSc91WRsaXjXtGr0Y/E8HfTT0QPtoIhOO8Dabkqn8KaAeI//CFlmdL4elDOUrNy+Dn/KmILFlwKi0nmxUoD0HtxJPkT1i7RmQ8T5NeQby3lufl8qgG0yuZWuD05GVattUt5d6aQmLs= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=b4akh5Ll; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="b4akh5Ll" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 2322AC4CEE4; Fri, 25 Apr 2025 17:51:46 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1745603506; bh=fpT/qX457YU2Zza6G3iWC4fjaELLorRrFMo5HBGKfiY=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=b4akh5LlBwBGX5t6unZl80JMMqiWd/P/kSjkcQotfTcysaCQC9dLqR0yqp1OxXPiZ MDomP/nOnWiUJ+LxP1sqyEHmNorSZL0sOuTXq/JiGAU7VYPfIZvWOi5H0H5PRIq9y/ L3EI2iiyDzr6JK+WLIJDGo2ZALrldegx+cwcWMZj7+qPjqRW3HuwRxArW61tP40ciO z+8dQkf5KZn8chwS9kQHwjhAoSlp50fQMuDnI8nvWb8rFfvjTwBRfDKM32pmsWyyLB 1DhXfgnwiISwabzhe6fVw5BwrrFyM7ESC8aprEeTxRhJw9bZjeTkJTXxtuHtZDZVbY Qi1MGzsFr10qQ== Date: Fri, 25 Apr 2025 10:51:45 -0700 From: Jakub Kicinski To: Jiri Pirko Cc: Moshe Shemesh , netdev@vger.kernel.org, "David S. Miller" , Eric Dumazet , Paolo Abeni , Simon Horman , Donald Hunter , Jonathan Corbet , Andrew Lunn , Tariq Toukan , Saeed Mahameed , Mark Bloch Subject: Re: [RFC net-next 0/5] devlink: Add unique identifier to devlink port function Message-ID: <20250425105145.6095c111@kernel.org> In-Reply-To: References: <1745416242-1162653-1-git-send-email-moshe@nvidia.com> <20250424162425.1c0b46d1@kernel.org> Precedence: bulk X-Mailing-List: netdev@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit On Fri, 25 Apr 2025 13:26:01 +0200 Jiri Pirko wrote: >> Makes sense, tho, could you please use UUID? >> Let's use industry standards when possible, not "arbitrary strings". > > Well, you could make the same request for serial number of asic and board. > Could be uuids too, but they aren't. I mean, it makes sense to have all > uids as uuid, but since the fw already exposes couple of uids as > arbitrary strings, why this one should be treated differently all of the > sudden? Are you asking me what the difference is here, or you're just telling me that I'm wrong and inconsistent?