From: "D. Manresa" <dmanresa@gmail.com>
To: Hans de Goede <hansg@kernel.org>
Cc: "Daniel Scally" <dan.scally@ideasonboard.com>,
"Sakari Ailus" <sakari.ailus@linux.intel.com>,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org, "D . Manresa" <dmanresa@gmail.com>
Subject: Re: int3472: discrete: 4-char GPIO supply name limit and unhandled vendor GPIO type 0x08 leave OV8865 unpowered (Surface Pro 7+)
Date: Mon, 31 Aug 2026 12:27:22 +0200 [thread overview]
Message-ID: <20260831102722.37615-1-dmanresa@gmail.com> (raw)
In-Reply-To: <daa8e671-adb3-4b67-93c4-d3779985d89b@kernel.org>
On Sun, 31 Aug 2026, Hans de Goede wrote:
> I wanted to review your patch for this, but that link does not work and
> lore.kernel.org does not have any patch with the mentioned title ?
You found the reason yourself a few minutes later on the patch thread: the
patch never reached the lists. A mail tooling error on my side was dropping
the Cc: headers on some sends (while keeping To:), so v1 went only to the
people named in To: and lore never saw it - hence the dead link. Same error
hit two of my replies on the ipu-bridge thread; all fixed now.
Resent as
[PATCH v2] platform/x86: int3472: map the ov7251 power enable GPIO to "vdda"
https://lore.kernel.org/platform-driver-x86/20260831102306.36610-1-dmanresa@gmail.com/
with platform-driver-x86 on Cc and your Reviewed-by collected - and thank you
for reviewing it from the direct copy despite the missing list posting.
D. Manresa <dmanresa@gmail.com>
prev parent reply other threads:[~2026-08-31 10:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-27 23:26 int3472: discrete: 4-char GPIO supply name limit and unhandled vendor GPIO type 0x08 leave OV8865 unpowered (Surface Pro 7+) D. Manresa
2026-08-30 12:32 ` Hans de Goede
[not found] ` <20260830150025.268353-1-dmanresa@gmail.com>
[not found] ` <daa8e671-adb3-4b67-93c4-d3779985d89b@kernel.org>
2026-08-31 10:27 ` D. Manresa [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=20260831102722.37615-1-dmanresa@gmail.com \
--to=dmanresa@gmail.com \
--cc=dan.scally@ideasonboard.com \
--cc=hansg@kernel.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@vger.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