From: Aliaksandr Smirnou <asmirnou@pinefeat.co.uk>
To: conor@kernel.org
Cc: asmirnou@pinefeat.co.uk, conor+dt@kernel.org,
devicetree@vger.kernel.org, hverkuil@xs4all.nl,
jacopo.mondi@ideasonboard.com, krzk+dt@kernel.org,
linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
mchehab@kernel.org, robh@kernel.org
Subject: Re: [PATCH v6 1/2] dt-bindings: Pinefeat cef168 lens control board
Date: Wed, 8 Oct 2025 18:50:36 +0100 [thread overview]
Message-ID: <20251008175036.8314-1-asmirnou@pinefeat.co.uk> (raw)
In-Reply-To: <20251007-obscure-thrower-1afcdb23c4b8@spud>
On Tue, 7 Oct 2025 21:47:29 +0100, Conor Dooley wrote:
> I acked v5, any reason for not applying it?
> https://lore.kernel.org/all/20251007-geologic-epidemic-2f667f232cf6@spud/#t
Yes, the dt-bindings patch can be applied.
The v6 series does not change anything in the dt-bindings patch - only
another patch in the series was updated, so v6 was sent.
Apologies - I wasn't aware that an acked patch could be omitted from
the new revision.
next prev parent reply other threads:[~2025-10-08 17:50 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-07 19:57 [PATCH v6 0/2] Pinefeat cef168 lens control board driver Aliaksandr Smirnou
2025-10-07 19:57 ` [PATCH v6 1/2] dt-bindings: Pinefeat cef168 lens control board Aliaksandr Smirnou
2025-10-07 20:47 ` Conor Dooley
2025-10-08 17:50 ` Aliaksandr Smirnou [this message]
2025-10-08 18:31 ` Conor Dooley
2025-10-08 21:32 ` Aliaksandr Smirnou
2025-10-08 23:46 ` Krzysztof Kozlowski
2025-10-09 20:17 ` Aliaksandr Smirnou
2025-10-07 19:57 ` [PATCH v6 2/2] media: i2c: Pinefeat cef168 lens control board driver Aliaksandr Smirnou
2026-05-26 15:54 ` [PATCH v6 0/2] " Alen Karnil
2026-05-26 20:35 ` Aliaksandr Smirnou
2026-05-27 11:45 ` Alen Karnil
2026-05-27 19:49 ` Aliaksandr Smirnou
2026-05-28 8:36 ` Alen Karnil
2026-05-30 11:46 ` Aliaksandr Smirnou
2026-06-01 8:59 ` Alen Karnil
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=20251008175036.8314-1-asmirnou@pinefeat.co.uk \
--to=asmirnou@pinefeat.co.uk \
--cc=conor+dt@kernel.org \
--cc=conor@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