mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Linus Torvalds <torvalds@linux-foundation.org>,
	Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, Stephen Rothwell <sfr@canb.auug.org.au>
Subject: [GIT PULL] Driver core addition for 6.14-rc3
Date: Sun, 16 Feb 2025 16:13:17 +0100	[thread overview]
Message-ID: <Z7IAjdCB8Ly5GIjW@kroah.com> (raw)

The following changes since commit a64dcfb451e254085a7daee5fe51bf22959d52d3:

  Linux 6.14-rc2 (2025-02-09 12:45:03 -0800)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core.git tags/driver-core-6.14-rc3

for you to fetch changes up to 78418f300d3999f1cf8a9ac71065bf2eca61f4dd:

  rust/kernel: Add faux device bindings (2025-02-13 16:58:58 +0100)

----------------------------------------------------------------
Driver core api addition for 6.14-rc3

Here is a driver core new api for 6.14-rc3 that is being added to allow
platform devices from stop being abused.  It adds a new "faux_device"
structure and bus and api to allow almost a straight or simpler
conversion from platform devices that were not really a platform device.
It also comes with a binding for rust, with an example driver in rust
showing how it's used.

I'm adding this now so that the patches that convert the different
drivers and subsystems can all start flowing into linux-next now through
their different development trees, in time for 6.15-rc1.  We have a
number that are already reviewed and tested, but adding those
conversions now doesn't seem right.  For now, no one is using this, and
it passes all build tests from 0-day and linux-next, so all should be
good.

Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

----------------------------------------------------------------
Greg Kroah-Hartman (1):
      driver core: add a faux bus for use when a simple device/bus is needed

Lyude Paul (1):
      rust/kernel: Add faux device bindings

 Documentation/driver-api/infrastructure.rst |   6 +
 MAINTAINERS                                 |   2 +
 drivers/base/Makefile                       |   2 +-
 drivers/base/base.h                         |   1 +
 drivers/base/faux.c                         | 232 ++++++++++++++++++++++++++++
 drivers/base/init.c                         |   1 +
 include/linux/device/faux.h                 |  69 +++++++++
 rust/bindings/bindings_helper.h             |   1 +
 rust/kernel/faux.rs                         |  67 ++++++++
 rust/kernel/lib.rs                          |   1 +
 samples/rust/Kconfig                        |  10 ++
 samples/rust/Makefile                       |   1 +
 samples/rust/rust_driver_faux.rs            |  29 ++++
 13 files changed, 421 insertions(+), 1 deletion(-)
 create mode 100644 drivers/base/faux.c
 create mode 100644 include/linux/device/faux.h
 create mode 100644 rust/kernel/faux.rs
 create mode 100644 samples/rust/rust_driver_faux.rs

             reply	other threads:[~2025-02-16 15:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-16 15:13 Greg KH [this message]
2025-02-16 21:03 ` pr-tracker-bot

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=Z7IAjdCB8Ly5GIjW@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=torvalds@linux-foundation.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

all inboxes | Powered by JetHome®