From: Greg KH <gregkh@linuxfoundation.org>
To: "Nilawar, Badal" <badal.nilawar@intel.com>
Cc: intel-xe@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org, anshuman.gupta@intel.com,
rodrigo.vivi@intel.com, alexander.usyskin@intel.com,
daniele.ceraolospurio@intel.com
Subject: Re: [PATCH v4 02/10] mei: late_bind: add late binding component driver
Date: Tue, 1 Jul 2025 10:17:36 +0200 [thread overview]
Message-ID: <2025070131-snaking-trolling-87dc@gregkh> (raw)
In-Reply-To: <a0e54703-721e-4e87-9962-7007771f947b@intel.com>
On Tue, Jul 01, 2025 at 01:37:36PM +0530, Nilawar, Badal wrote:
>
> On 28-06-2025 17:49, Greg KH wrote:
> > On Wed, Jun 25, 2025 at 10:30:07PM +0530, Badal Nilawar wrote:
> > > +/**
> > > + * struct late_bind_component_ops - ops for Late Binding services.
> > > + * @owner: Module providing the ops
> > > + * @push_config: Sends a config to FW.
> > > + */
> > > +struct late_bind_component_ops {
> > > + struct module *owner;
> > I don't think you ever set this field, so why is it here?
> >
> > Or did I miss it somewhere?
>
> It is set in drivers/misc/mei/late_bind/mei_late_bind.c
>
> static const struct late_bind_component_ops mei_late_bind_ops = {
> .owner = THIS_MODULE,
> .push_config = mei_late_bind_push_config,
> };
Ah. But then who uses it? And why? Normally forcing callers to set
.owner is frowned apon, use a #define correctly to have it automatically
set for you in the registration function please.
And are you _sure_ you need it?
thanks,
greg k-h
next prev parent reply other threads:[~2025-07-01 8:17 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-25 17:00 [PATCH v4 00/10] Introducing firmware late binding Badal Nilawar
2025-06-25 17:00 ` [PATCH v4 01/10] mei: bus: add mei_cldev_mtu interface Badal Nilawar
2025-06-25 17:00 ` [PATCH v4 02/10] mei: late_bind: add late binding component driver Badal Nilawar
2025-06-26 3:50 ` Gupta, Anshuman
2025-06-27 14:06 ` Nilawar, Badal
2025-06-28 12:18 ` Greg KH
2025-07-01 8:32 ` Nilawar, Badal
2025-07-01 9:45 ` Greg KH
2025-07-01 12:34 ` Nilawar, Badal
2025-07-01 16:41 ` Nilawar, Badal
2025-07-01 17:34 ` Rodrigo Vivi
2025-07-02 4:12 ` Gupta, Anshuman
2025-07-02 6:24 ` Usyskin, Alexander
2025-07-01 10:05 ` Usyskin, Alexander
2025-06-28 12:19 ` Greg KH
2025-07-01 8:07 ` Nilawar, Badal
2025-07-01 8:17 ` Greg KH [this message]
2025-07-01 8:22 ` Nilawar, Badal
2025-07-01 8:32 ` Usyskin, Alexander
2025-06-25 17:00 ` [PATCH v4 03/10] drm/xe/xe_late_bind_fw: Introducing xe_late_bind_fw Badal Nilawar
2025-06-27 21:04 ` Rodrigo Vivi
2025-06-30 13:49 ` Nilawar, Badal
2025-06-25 17:00 ` [PATCH v4 04/10] drm/xe/xe_late_bind_fw: Initialize late binding firmware Badal Nilawar
2025-06-26 21:06 ` Daniele Ceraolo Spurio
2025-06-27 12:48 ` Nilawar, Badal
2025-06-25 17:00 ` [PATCH v4 05/10] drm/xe/xe_late_bind_fw: Load " Badal Nilawar
2025-06-26 17:24 ` Rodrigo Vivi
2025-06-26 21:27 ` Daniele Ceraolo Spurio
2025-06-26 21:49 ` Rodrigo Vivi
2025-06-26 22:38 ` Daniele Ceraolo Spurio
2025-06-26 22:49 ` Rodrigo Vivi
2025-06-25 17:00 ` [PATCH v4 06/10] drm/xe/xe_late_bind_fw: Reload late binding fw in rpm resume Badal Nilawar
2025-06-25 17:00 ` [PATCH v4 07/10] drm/xe/xe_late_bind_fw: Reload late binding fw during system resume Badal Nilawar
2025-06-27 7:53 ` Nilawar, Badal
2025-06-25 17:00 ` [PATCH v4 08/10] drm/xe/xe_late_bind_fw: Introduce debug fs node to disable late binding Badal Nilawar
2025-06-25 17:00 ` [PATCH v4 09/10] drm/xe/xe_late_bind_fw: Extract and print version info Badal Nilawar
2025-06-26 21:32 ` Daniele Ceraolo Spurio
2025-06-25 17:00 ` [PATCH v4 10/10] drm/xe/xe_late_bind_fw: Select INTEL_MEI_LATE_BIND for CI Badal Nilawar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2025070131-snaking-trolling-87dc@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=alexander.usyskin@intel.com \
--cc=anshuman.gupta@intel.com \
--cc=badal.nilawar@intel.com \
--cc=daniele.ceraolospurio@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rodrigo.vivi@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®