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.16-rc6
Date: Sun, 20 Jul 2025 12:46:17 +0200 [thread overview]
Message-ID: <aHzI-b5Kiy_Nu6l-@kroah.com> (raw)
The following changes since commit d0b3b7b22dfa1f4b515fd3a295b3fd958f9e81af:
Linux 6.16-rc4 (2025-06-29 13:09:04 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git tags/staging-6.16-rc6
for you to fetch changes up to f2b8ebfb867011ddbefbdf7b04ad62626cbc2afd:
staging: vchiq_arm: Make vchiq_shutdown never fail (2025-07-16 09:36:50 +0200)
----------------------------------------------------------------
Staging driver fixes for 6.16-rc6
Here are some small driver fixes for the vchiq_arm staging driver:
- reverts of previous changes that turned out to caused problems.
- change to prevent a research leak
All of these have been in linux-next this week with no reported
problems.
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
----------------------------------------------------------------
Stefan Wahren (3):
Revert "staging: vchiq_arm: Improve initial VCHIQ connect"
Revert "staging: vchiq_arm: Create keep-alive thread during probe"
staging: vchiq_arm: Make vchiq_shutdown never fail
.../vc04_services/interface/vchiq_arm/vchiq_arm.c | 98 ++++++++++++----------
.../vc04_services/interface/vchiq_arm/vchiq_core.c | 1 -
.../vc04_services/interface/vchiq_arm/vchiq_core.h | 2 -
3 files changed, 56 insertions(+), 45 deletions(-)
next reply other threads:[~2025-07-20 10:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-20 10:46 Greg KH [this message]
2025-07-20 16:10 ` Linus Torvalds
2025-07-20 16:31 ` 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=aHzI-b5Kiy_Nu6l-@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®