Linux Documentation
 help / color / mirror / Atom feed
From: "Uwe Kleine-König" <u.kleine-koenig@baylibre.com>
To: "M, Krishnamoorthi" <krishnamoorthi.m@amd.com>
Cc: linux-kernel@vger.kernel.org, gregkh@linuxfoundation.org,
	 broonie@kernel.org, linux-spi@vger.kernel.org,
	akshata.mukundshetty@amd.com,  bleung@chromium.org,
	groeck@chromium.org, chrome-platform@lists.linux.dev,
	 corbet@lwn.net, linux-doc@vger.kernel.org,
	skhan@linuxfoundation.org,  andrew@codeconstruct.com.au,
	linux-aspeed@lists.ozlabs.org, openbmc@lists.ozlabs.org
Subject: Re: [RFC PATCH 1/4] espi: add core bus framework
Date: Wed, 12 Aug 2026 18:30:00 +0200	[thread overview]
Message-ID: <anye28kId4k8pxBv@monoceros> (raw)
In-Reply-To: <0f7469b8-8275-4061-b336-97cbce41ff82@amd.com>

[-- Attachment #1: Type: text/plain, Size: 882 bytes --]

Hello,

On Wed, Aug 12, 2026 at 06:20:29PM +0530, M, Krishnamoorthi wrote:
> On 8/6/2026 7:01 PM, Uwe Kleine-König wrote:
> > On Tue, Aug 04, 2026 at 05:22:56PM +0530, Krishnamoorthi M wrote:
> > > [...]
> > > +const struct bus_type espi_bus_type = {
> > > +	.name	= "espi",
> > > +	.match	= espi_bus_match,
> > > +	.uevent	= espi_bus_uevent,
> > > +	.probe	= espi_bus_probe,
> > > +	.remove	= espi_bus_remove,
> > > +};
> > > +EXPORT_SYMBOL_GPL(espi_bus_type);
> > 
> > Do you really need this exported?
> 
> Yes, it is required. Controller and slave drivers built as modules reference
> espi_bus_type directly when registering devices. Without the export they
> fail to link.

I would have expected that

	drv->driver.bus = &espi_bus_type;

in __espi_register_driver() is enough for drivers to not have to use
that symbol directly?

Best regards
Uwe

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2026-08-12 16:30 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-04 11:52 [RFC PATCH 0/4] espi: introduce eSPI bus framework Krishnamoorthi M
2026-08-04 11:52 ` [RFC PATCH 1/4] espi: add core " Krishnamoorthi M
2026-08-06 13:31   ` Uwe Kleine-König
2026-08-12 12:50     ` M, Krishnamoorthi
2026-08-12 16:30       ` Uwe Kleine-König [this message]
2026-08-04 11:52 ` [RFC PATCH 2/4] espi: add slave device model and event notification Krishnamoorthi M
2026-08-04 11:52 ` [RFC PATCH 3/4] Documentation: espi: add subsystem overview and MAINTAINERS entry Krishnamoorthi M
2026-08-04 16:39   ` Randy Dunlap
2026-08-04 19:14     ` M, Krishnamoorthi
2026-08-04 11:52 ` [RFC PATCH 4/4] espi: amd: add AMD eSPI controller driver Krishnamoorthi M
2026-08-04 12:18 ` [RFC PATCH 0/4] espi: introduce eSPI bus framework Greg KH
2026-08-04 13:26   ` Greg KH
2026-08-05  0:42   ` Andrew Jeffery
2026-08-05 18:35     ` M, Krishnamoorthi
2026-08-10  6:13       ` YH Chung
2026-08-05 10:14   ` M, Krishnamoorthi

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=anye28kId4k8pxBv@monoceros \
    --to=u.kleine-koenig@baylibre.com \
    --cc=akshata.mukundshetty@amd.com \
    --cc=andrew@codeconstruct.com.au \
    --cc=bleung@chromium.org \
    --cc=broonie@kernel.org \
    --cc=chrome-platform@lists.linux.dev \
    --cc=corbet@lwn.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=groeck@chromium.org \
    --cc=krishnamoorthi.m@amd.com \
    --cc=linux-aspeed@lists.ozlabs.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=openbmc@lists.ozlabs.org \
    --cc=skhan@linuxfoundation.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