From: Hans de Goede <hansg@kernel.org>
To: Daniel Scally <djrscally@gmail.com>,
Sakari Ailus <sakari.ailus@linux.intel.com>
Cc: Hans de Goede <hansg@kernel.org>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
linux-media@vger.kernel.org
Subject: [PATCH 0/4] media: i2c/pci: Various error logging improvements
Date: Mon, 23 Jun 2025 13:00:31 +0200 [thread overview]
Message-ID: <20250623110035.18340-1-hansg@kernel.org> (raw)
Hi all,
Here is a resend of a bunch or error logging improvements which I send
out last year, but which seem to have fallen through the cracks.
Regards,
Hans
Hans de Goede (4):
media: ov5693: Improve error logging when fwnode is not found
media: ov7251: Improve error logging when fwnode is not found
media: ov8865: Improve error logging when fwnode is not found
media: ipu-bridge: Improve error logging when waiting for IVSC to
become ready
drivers/media/i2c/ov5693.c | 7 ++++++-
drivers/media/i2c/ov7251.c | 7 ++++++-
drivers/media/i2c/ov8865.c | 3 ++-
drivers/media/pci/intel/ipu-bridge.c | 3 ++-
4 files changed, 16 insertions(+), 4 deletions(-)
--
2.49.0
next reply other threads:[~2025-06-23 11:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-23 11:00 Hans de Goede [this message]
2025-06-23 11:00 ` [PATCH 1/4] media: ov5693: Improve error logging when fwnode is not found Hans de Goede
2025-06-24 12:43 ` Daniel Scally
2025-06-23 11:00 ` [PATCH 2/4] media: ov7251: " Hans de Goede
2025-06-24 12:44 ` Daniel Scally
2025-06-23 11:00 ` [PATCH 3/4] media: ov8865: " Hans de Goede
2025-06-24 12:44 ` Daniel Scally
2025-06-23 11:00 ` [PATCH 4/4] media: ipu-bridge: Improve error logging when waiting for IVSC to become ready Hans de Goede
2025-06-24 12:44 ` Daniel Scally
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=20250623110035.18340-1-hansg@kernel.org \
--to=hansg@kernel.org \
--cc=djrscally@gmail.com \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=sakari.ailus@linux.intel.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