From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Jose Javier Rodriguez Barbarin <dev-josejavier.rodriguez@duagon.com>
Cc: andy@kernel.org, krzk@kernel.org, linus.walleij@linaro.org,
nathan@kernel.org, nsc@kernel.org, gregkh@linuxfoundation.org,
bleung@chromium.org, heikki.krogerus@linux.intel.com,
abhishekpandit@chromium.org, masahiroy@kernel.org,
legion@kernel.org, hughd@google.com,
linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org,
Jorge Sanjuan Garcia <dev-jorge.sanjuangarcia@duagon.com>
Subject: Re: [PATCH v2 1/1] mcb: Add missing modpost build support
Date: Mon, 1 Dec 2025 20:02:57 +0200 [thread overview]
Message-ID: <aS3YUYtrEn39lUPl@smile.fi.intel.com> (raw)
In-Reply-To: <20251201160720.28580-2-dev-josejavier.rodriguez@duagon.com>
On Mon, Dec 01, 2025 at 05:07:20PM +0100, Jose Javier Rodriguez Barbarin wrote:
> mcb bus is not prepared to autoload client drivers with the data defined on
> the drivers' MODULE_DEVICE_TABLE. modpost cannot access to mcb_table_id
> inside MODULE_DEVICE_TABLE so the data declared inside is ignored.
>
> Add modpost build support for accessing to the mcb_table_id coded on device
> drivers' MODULE_DEVICE_TABLE.
I believe the idea to add Fixes tag here and make sure it goes to v6.19-rcX.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2025-12-01 18:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-01 16:07 [PATCH v2 0/1] mcb: Add modpost support for processing MODULE_DEVICE_TABLE Jose Javier Rodriguez Barbarin
2025-12-01 16:07 ` [PATCH v2 1/1] mcb: Add missing modpost build support Jose Javier Rodriguez Barbarin
2025-12-01 18:02 ` Andy Shevchenko [this message]
2025-12-01 18:04 ` [PATCH v2 0/1] mcb: Add modpost support for processing MODULE_DEVICE_TABLE Andy Shevchenko
2025-12-01 18:26 ` Jose Javier Rodriguez Barbarin
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=aS3YUYtrEn39lUPl@smile.fi.intel.com \
--to=andriy.shevchenko@intel.com \
--cc=abhishekpandit@chromium.org \
--cc=andy@kernel.org \
--cc=bleung@chromium.org \
--cc=dev-jorge.sanjuangarcia@duagon.com \
--cc=dev-josejavier.rodriguez@duagon.com \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=hughd@google.com \
--cc=krzk@kernel.org \
--cc=legion@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=nathan@kernel.org \
--cc=nsc@kernel.org \
/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