From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mgamail.intel.com (mgamail.intel.com [192.55.52.93]) (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 ACE6D23A6; Sun, 14 Jan 2024 17:08:20 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.intel.com Authentication-Results: smtp.subspace.kernel.org; spf=none smtp.mailfrom=linux.intel.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=intel.com header.i=@intel.com header.b="YEKWtib+" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1705252100; x=1736788100; h=date:from:to:cc:subject:message-id:references: mime-version:content-transfer-encoding:in-reply-to; bh=UzgFjM2CD1QtXNQP46Z3RkFdGjU5fivGIZd8OKaOVwY=; b=YEKWtib+YqxYs6DzJO6TN8gzeyExwgQufbV6MRG5kGNBQQpzt2KjJuaZ VEw49nocHXsxESG4648px4qLFoj+G3oJOgpVaxCCaNe9JXDcROfU9nMqS 6OrdZq97CSnLlLa7jb32Kki9CoF3Q/CZbSLM+u+YlsCWI0TmuJpeuQSqS C42wo33JBV4jysQZHekLCh+BFk4YYx0AOZTTDs/uZcPg5Qx04gWa5OvCG 2nGRB49ZDszXrNvDef8QfCBGrfrIJN2ltHGIsDCpc4lW9thGGt+u0qUEC 8l/FwVst4M7SgF0fIZL5BBNltX39Z+3rHfZru8ZOSxlzcC32bff40J8oO w==; X-IronPort-AV: E=McAfee;i="6600,9927,10953"; a="396621295" X-IronPort-AV: E=Sophos;i="6.04,194,1695711600"; d="scan'208";a="396621295" Received: from fmsmga007.fm.intel.com ([10.253.24.52]) by fmsmga102.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 14 Jan 2024 09:08:19 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=McAfee;i="6600,9927,10953"; a="786869958" X-IronPort-AV: E=Sophos;i="6.04,194,1695711600"; d="scan'208";a="786869958" Received: from smile.fi.intel.com ([10.237.72.54]) by fmsmga007.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 14 Jan 2024 09:08:16 -0800 Received: from andy by smile.fi.intel.com with local (Exim 4.97) (envelope-from ) id 1rP3y1-0000000DyAP-1bfe; Sun, 14 Jan 2024 19:08:13 +0200 Date: Sun, 14 Jan 2024 19:08:13 +0200 From: Andy Shevchenko To: =?iso-8859-1?Q?N=EDcolas_F=2E_R=2E_A=2E?= Prado Cc: Tzung-Bi Shih , kernel@collabora.com, AngeloGioacchino Del Regno , Abhijit Gangurde , Greg Kroah-Hartman , Masahiro Yamada , Nathan Chancellor , Nicolas Schier , Nipun Gupta , Pieter Jansen van Vuuren , Umang Jain , linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH 2/4] firmware: coreboot: Generate aliases for coreboot modules Message-ID: References: <20240111151226.842603-1-nfraprado@collabora.com> <20240111151226.842603-3-nfraprado@collabora.com> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20240111151226.842603-3-nfraprado@collabora.com> Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo On Thu, Jan 11, 2024 at 12:11:47PM -0300, Nícolas F. R. A. Prado wrote: > Generate aliases for coreboot modules to allow automatic module probing. ... > +/** > + * struct coreboot_device_id - Identifies a coreboot table entry > + * @tag: tag ID > + */ > +struct coreboot_device_id { > + __u32 tag; > +}; Don't you want to have a driver data or so associated with this? -- With Best Regards, Andy Shevchenko