linux-spi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Mark Brown <broonie@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-spi@vger.kernel.org
Subject: Re: [PATCH] spi: make spi_bus_type const
Date: Fri, 5 Jan 2024 16:05:18 +0100	[thread overview]
Message-ID: <2024010554-unreached-colony-96dd@gregkh> (raw)
In-Reply-To: <0fcee73a-bdcb-41d5-b6e5-21947ae9e3d7@sirena.org.uk>

On Fri, Jan 05, 2024 at 02:55:01PM +0000, Mark Brown wrote:
> On Fri, Jan 05, 2024 at 11:32:50AM +0100, Greg Kroah-Hartman wrote:
> > Now that the driver core can properly handle constant struct bus_type,
> > move the spi_bus_type variable to be a constant structure as well,
> > placing it into read-only memory which can not be modified at runtime.
> 
> Whatever makes the driver core able to handle this doesn't seem to be in
> mainline yet - what's the story there?

Odd, what errors are you seeing when you build?  I have had to fix up a
few subsys_* calls for this type of thing, but I don't see spi_bus_type
being used in those that I saw in my local tree.  Did I miss something
else?

Maybe just wait for after 6.8-rc1, it builds properly here locally :)

thanks,

greg k-h

  reply	other threads:[~2024-01-05 15:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-05 10:32 [PATCH] spi: make spi_bus_type const Greg Kroah-Hartman
2024-01-05 14:55 ` Mark Brown
2024-01-05 15:05   ` Greg Kroah-Hartman [this message]
2024-01-05 15:45     ` Mark Brown
2024-01-05 15:51       ` Greg Kroah-Hartman
2024-01-05 15:59         ` Mark Brown
2024-01-05 16:02           ` Greg Kroah-Hartman
2024-01-22 16:49 ` Mark Brown

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=2024010554-unreached-colony-96dd@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=broonie@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-spi@vger.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;
as well as URLs for NNTP newsgroup(s).