From: Bryan O'Donoghue <bod@kernel.org>
To: Jakob Berg Jespersen <dev@berg.pm>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Daniel Scally <dan.scally@ideasonboard.com>
Cc: Hans de Goede <hansg@kernel.org>,
Fernando Rimoli <fernandorimoli11@gmail.com>,
Tooraj Taraz <tooraj.taraz@yahoo.com>,
"Joseph V. Lavigne" <jlavig88@gmail.com>,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH RFC 0/2] media: i2c: Surface Pro 7+ camera flip fixes
Date: Wed, 22 Jul 2026 23:14:21 +0100 [thread overview]
Message-ID: <11ca0787-e990-4f49-a409-fd96a48e2238@kernel.org> (raw)
In-Reply-To: <20260720-sp7plus-ov-flips-v1-0-5f345b0673de@berg.pm>
On 20/07/2026 15:28, Jakob Berg Jespersen wrote:
> This RFC series fixes two horizontal-flip issues on the front and rear
> cameras of the Microsoft Surface Pro 7+ (Tiger Lake IPU6, ACPI/ipu-bridge).
> Both were found and validated on real hardware (Surface Pro 7+, Fedora 44,
> kernel 7.0.12) and have been in daily use on that machine for over a
> month; each is described in detail in its own patch.
From a pure process point of view.
Anything that fixes a bug should have a Fixes: and a Cc: stable,
especially granular stuff like in this series.
Please add both.
---
bod
prev parent reply other threads:[~2026-07-22 22:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Q5OH0unwBM9QICxTJXBm1W7LkqYpiGtPRvNqI8FMsDW63Z1AgVArhC3__6dhY4hjrsuDCsbMfvArNyf_qB0Akw==@protonmail.internalid>
2026-07-20 14:28 ` [PATCH RFC 0/2] media: i2c: Surface Pro 7+ camera flip fixes Jakob Berg Jespersen
2026-07-20 14:28 ` [PATCH RFC 1/2] media: i2c: ov8865: fix horizontal flip control polarity Jakob Berg Jespersen
2026-07-28 22:30 ` Sakari Ailus
2026-07-29 13:15 ` Hans de Goede
2026-07-29 13:13 ` Hans de Goede
2026-07-20 14:28 ` [PATCH RFC 2/2] media: i2c: ov5693: fix horizontal flip polarity and Bayer phase Jakob Berg Jespersen
2026-07-20 17:39 ` Fernando Rimoli
2026-07-29 13:18 ` Hans de Goede
2026-07-22 22:14 ` Bryan O'Donoghue [this message]
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=11ca0787-e990-4f49-a409-fd96a48e2238@kernel.org \
--to=bod@kernel.org \
--cc=dan.scally@ideasonboard.com \
--cc=dev@berg.pm \
--cc=fernandorimoli11@gmail.com \
--cc=hansg@kernel.org \
--cc=jlavig88@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=sakari.ailus@linux.intel.com \
--cc=tooraj.taraz@yahoo.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