From: Krzysztof Kozlowski <krzk@kernel.org>
To: Aliaksandr Smirnou <asmirnou@pinefeat.co.uk>,
jacopo.mondi@ideasonboard.com, hverkuil@xs4all.nl,
mchehab@kernel.org, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org
Cc: devicetree@vger.kernel.org, linux-media@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 0/2] Pinefeat cef168 lens control board driver
Date: Sat, 30 Aug 2025 15:20:30 +0200 [thread overview]
Message-ID: <436efc30-5e54-43c4-9d68-88bc63d71231@kernel.org> (raw)
In-Reply-To: <20250830111500.53169-1-asmirnou@pinefeat.co.uk>
On 30/08/2025 13:14, Aliaksandr Smirnou wrote:
> This patch series adds support for the Pinefeat adapter, which interfaces
> Canon EF and EF-S lenses to non-Canon camera bodies. The cef168 circuit
> control board provides an I2C interface for electronic focus and aperture
> control. The driver integrates with the V4L2 sub-device API.
>
> For more information about the product, see:
> https://github.com/pinefeat/cef168
>
> Changes in v4:
You already sent v4, so this makes a duplicate posting messing up with
tools.
https://lore.kernel.org/all/20250824-cuddly-cryptic-porpoise-b66b4a@kuoka/
Each posting is its own version. Resending - not marked here as resend -
would be sending the same patch.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-08-30 13:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-30 11:14 Aliaksandr Smirnou
2025-08-30 11:14 ` [PATCH v4 1/2] dt-bindings: Pinefeat cef168 lens control board Aliaksandr Smirnou
2025-08-30 13:21 ` Krzysztof Kozlowski
2025-08-30 14:24 ` Kieran Bingham
2025-08-30 15:53 ` Konstantin Ryabitsev
2025-08-30 15:58 ` Aliaksandr Smirnou
2025-08-30 11:15 ` [PATCH v4 2/2] media: i2c: Pinefeat cef168 lens control board driver Aliaksandr Smirnou
2025-08-30 13:20 ` Krzysztof Kozlowski [this message]
2025-09-21 18:52 ` [PATCH v4 0/2] " Aliaksandr Smirnou
-- strict thread matches above, loose matches on Subject: below --
2025-08-22 17:10 Aliaksandr Smirnou
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=436efc30-5e54-43c4-9d68-88bc63d71231@kernel.org \
--to=krzk@kernel.org \
--cc=asmirnou@pinefeat.co.uk \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=hverkuil@xs4all.nl \
--cc=jacopo.mondi@ideasonboard.com \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=robh@kernel.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
all inboxes | Powered by JetHome®