From: Greg KH <gregkh@linuxfoundation.org>
To: Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-kernel@vger.kernel.org, linux-staging@lists.linux.dev
Subject: [GIT PULL] Staging driver fixes for 6.10-rc6
Date: Sun, 30 Jun 2024 16:12:23 +0200 [thread overview]
Message-ID: <ZoFnxy7Wy7fI_iDL@kroah.com> (raw)
The following changes since commit 6ba59ff4227927d3a8530fc2973b80e94b54d58f:
Linux 6.10-rc4 (2024-06-16 13:40:16 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git tags/staging-6.10-rc6
for you to fetch changes up to fcdd7b7bda3c21d1ba1247419e4a1eb8e2d0bfbb:
staging: vchiq_debugfs: Fix build if CONFIG_DEBUG_FS is not set (2024-06-27 15:47:30 +0200)
----------------------------------------------------------------
Staging driver fixes for 6.10-rc6
Here are 2 small staging driver fixes for 6.10-rc6, both for the
vc04_services drivers:
- build fix if CONFIG_DEBUGFS was not set
- initialization check fix that was much reported.
Both of these have been in linux-next this week with no reported issues.
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
----------------------------------------------------------------
Bernhard Rosenkränzer (1):
staging: vchiq_debugfs: Fix build if CONFIG_DEBUG_FS is not set
Kieran Bingham (1):
staging: vc04_services: vchiq_arm: Fix initialisation check
drivers/staging/vc04_services/interface/vchiq_arm/vchiq_arm.c | 4 ++--
drivers/staging/vc04_services/interface/vchiq_arm/vchiq_core.h | 5 +++++
drivers/staging/vc04_services/interface/vchiq_arm/vchiq_debugfs.c | 2 +-
drivers/staging/vc04_services/interface/vchiq_arm/vchiq_dev.c | 7 ++++++-
4 files changed, 14 insertions(+), 4 deletions(-)
next reply other threads:[~2024-06-30 14:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-30 14:12 Greg KH [this message]
2024-06-30 16:28 ` 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=ZoFnxy7Wy7fI_iDL@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--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®