From: Greg KH <gregkh@linuxfoundation.org>
To: Nathan Chancellor <nathan@kernel.org>
Cc: Jose Javier Rodriguez Barbarin
<dev-josejavier.rodriguez@duagon.com>,
andy@kernel.org, krzk@kernel.org, linus.walleij@linaro.org,
nsc@kernel.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 v3] mcb: Add missing modpost build support
Date: Wed, 3 Dec 2025 09:07:02 +0100 [thread overview]
Message-ID: <2025120340-clubbing-stash-a933@gregkh> (raw)
In-Reply-To: <20251202203421.GB1959956@ax162>
On Tue, Dec 02, 2025 at 01:34:21PM -0700, Nathan Chancellor wrote:
> On Tue, Dec 02, 2025 at 09:42:00AM +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.
> >
> > Fixes: 3764e82e5150 ("drivers: Introduce MEN Chameleon Bus")
> > Reviewed-by: Jorge Sanjuan Garcia <dev-jorge.sanjuangarcia@duagon.com>
> > Signed-off-by: Jose Javier Rodriguez Barbarin <dev-josejavier.rodriguez@duagon.com>
> > ---
>
> Acked-by: Nathan Chancellor <nathan@kernel.org>
>
> We should be able to get this to Linus by 6.19-rc1.
Why? What's the rush? It should have been in -next already to get into
-rc1.
thanks,
greg k-h
next prev parent reply other threads:[~2025-12-03 8:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-02 8:42 [PATCH v3] mcb: Add missing modpost build support Jose Javier Rodriguez Barbarin
2025-12-02 14:37 ` Andy Shevchenko
2025-12-02 20:34 ` Nathan Chancellor
2025-12-03 8:07 ` Greg KH [this message]
2025-12-03 20:27 ` Nathan Chancellor
2025-12-27 20:10 ` Nicolas Schier
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=2025120340-clubbing-stash-a933@gregkh \
--to=gregkh@linuxfoundation.org \
--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=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