public inbox for linux-kernel@vger.kernel.org
 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 fixes for 6.15-rc6
Date: Sat, 10 May 2025 15:53:42 +0200	[thread overview]
Message-ID: <aB9aZjUU3BShkFyd@kroah.com> (raw)

The following changes since commit 0af2f6be1b4281385b618cb86ad946eded089ac8:

  Linux 6.15-rc1 (2025-04-06 13:11:33 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git tags/staging-6.15-rc6

for you to fetch changes up to c6e8d85fafa7193613db37da29c0e8d6e2515b13:

  staging: axis-fifo: Remove hardware resets for user errors (2025-04-25 16:14:25 +0200)

----------------------------------------------------------------
Staging driver fixes for 6.15-rc6

Here are three small staging driver fixes for 6.15-rc6.  These are:
  - bcm2835-camera driver fix
  - two axis-fifo driver fixes

All of these have been in linux-next for a few weeks with no reported
issues.

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

----------------------------------------------------------------
Dave Stevenson (1):
      staging: bcm2835-camera: Initialise dev in v4l2_dev

Gabriel Shahrouzi (2):
      staging: axis-fifo: Correct handling of tx_fifo_depth for size validation
      staging: axis-fifo: Remove hardware resets for user errors

 drivers/staging/axis-fifo/axis-fifo.c                      | 14 +++-----------
 .../staging/vc04_services/bcm2835-camera/bcm2835-camera.c  |  1 +
 2 files changed, 4 insertions(+), 11 deletions(-)

             reply	other threads:[~2025-05-10 13:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-10 13:53 Greg KH [this message]
2025-05-10 16:29 ` [GIT PULL] Staging driver fixes for 6.15-rc6 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=aB9aZjUU3BShkFyd@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