From: Naushir Patuck <naush@raspberrypi.com>
To: Raspberry Pi Kernel Maintenance <kernel-list@raspberrypi.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Florian Fainelli <florian.fainelli@broadcom.com>,
Broadcom internal kernel review list
<bcm-kernel-feedback-list@broadcom.com>,
Ray Jui <rjui@broadcom.com>,
Scott Branden <sbranden@broadcom.com>
Cc: linux-media@vger.kernel.org,
linux-rpi-kernel@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, jacopo.mondi@ideasonboard.com,
Dave Stevenson <dave.stevenson@raspberrypi.com>,
Naushir Patuck <naush@raspberrypi.com>
Subject: [PATCH v2 0/4] media: bcm2835-unicam: Upstreaming various improvements
Date: Wed, 27 Nov 2024 11:15:11 +0000 [thread overview]
Message-ID: <20241127111515.565992-1-naush@raspberrypi.com> (raw)
Hi,
Version 2 of this series has no changes, except patch 5/5 from v1 has been
removed while I rework the logic donwstream first.
Thanks,
Naush
Naushir Patuck (4):
drivers: media: bcm2835-unicam: Improve frame sequence count handling
drivers: media: bcm2835-unicam: Allow setting of unpacked formats
drivers: media: bcm2835-unicam: Disable trigger mode operation
drivers: media: bcm2835-unicam: Fix for possible dummy buffer overrun
.../media/platform/broadcom/bcm2835-unicam.c | 42 ++++++++++++++-----
1 file changed, 31 insertions(+), 11 deletions(-)
--
2.34.1
next reply other threads:[~2024-11-27 11:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-27 11:15 Naushir Patuck [this message]
2024-11-27 11:15 ` [PATCH v2 1/4] drivers: media: bcm2835-unicam: Improve frame sequence count handling Naushir Patuck
2024-11-27 11:15 ` [PATCH v2 2/4] drivers: media: bcm2835-unicam: Allow setting of unpacked formats Naushir Patuck
2024-11-27 11:15 ` [PATCH v2 3/4] drivers: media: bcm2835-unicam: Disable trigger mode operation Naushir Patuck
2024-11-27 11:15 ` [PATCH v2 4/4] drivers: media: bcm2835-unicam: Fix for possible dummy buffer overrun Naushir Patuck
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=20241127111515.565992-1-naush@raspberrypi.com \
--to=naush@raspberrypi.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=dave.stevenson@raspberrypi.com \
--cc=florian.fainelli@broadcom.com \
--cc=jacopo.mondi@ideasonboard.com \
--cc=kernel-list@raspberrypi.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=mchehab@kernel.org \
--cc=rjui@broadcom.com \
--cc=sbranden@broadcom.com \
/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®