Linux kernel staging patches
 help / color / mirror / Atom feed
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 fix for 6.10-rc4
Date: Sun, 16 Jun 2024 12:51:28 +0200	[thread overview]
Message-ID: <Zm7DsDUAGWwEE6Lf@kroah.com> (raw)

The following changes since commit c3f38fa61af77b49866b006939479069cd451173:

  Linux 6.10-rc2 (2024-06-02 15:44:56 -0700)

are available in the Git repository at:

  ssh://git@gitolite.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git tags/staging-6.10-rc4

for you to fetch changes up to c3552ab19aeb8101b751e7c7ad45deab9e1134e1:

  staging: vchiq_debugfs: Fix NPD in vchiq_dump_state (2024-06-04 13:36:44 +0200)

----------------------------------------------------------------
Staging driver fix for 6.10-rc4

Here is a single staging driver fix, for the vc04 driver, for 6.10-rc4.
It resolves a reported problem that showed up in the 6.10-rc1 set of
changes.

It's been in linux-next for over a week with no reported problems.

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

----------------------------------------------------------------
Stefan Wahren (1):
      staging: vchiq_debugfs: Fix NPD in vchiq_dump_state

 drivers/staging/vc04_services/interface/vchiq_arm/vchiq_arm.c     | 2 +-
 drivers/staging/vc04_services/interface/vchiq_arm/vchiq_debugfs.c | 8 ++++----
 drivers/staging/vc04_services/interface/vchiq_arm/vchiq_debugfs.h | 2 +-
 3 files changed, 6 insertions(+), 6 deletions(-)

             reply	other threads:[~2024-06-16 10:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-16 10:51 Greg KH [this message]
2024-06-16 18:24 ` [GIT PULL] Staging driver fix for 6.10-rc4 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=Zm7DsDUAGWwEE6Lf@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