[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <49b42da1-a74b-433c-b018-0742f850f680@notapiano>
Date: Wed, 17 Jan 2024 09:53:23 -0300
From: Nícolas F. R. A. Prado <nfraprado@...labora.com>
To: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
Cc: Tzung-Bi Shih <tzungbi@...nel.org>, kernel@...labora.com,
AngeloGioacchino Del Regno <angelogioacchino.delregno@...labora.com>,
Abhijit Gangurde <abhijit.gangurde@....com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Masahiro Yamada <masahiroy@...nel.org>,
Nathan Chancellor <nathan@...nel.org>,
Nicolas Schier <nicolas@...sle.eu>,
Nipun Gupta <nipun.gupta@....com>,
Pieter Jansen van Vuuren <pieter.jansen-van-vuuren@....com>,
Umang Jain <umang.jain@...asonboard.com>,
linux-kbuild@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2/4] firmware: coreboot: Generate aliases for coreboot
modules
On Sun, Jan 14, 2024 at 07:08:13PM +0200, Andy Shevchenko wrote:
> 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?
There's no need for it currently in any driver. This struct is being created
simply to allow auto modprobe. So it seems reasonable to leave it out and add it
later when/if needed.
Thanks,
Nícolas
Powered by blists - more mailing lists