From: Alen Karnil <alen.karnil@ideasonboard.com>
To: Aliaksandr Smirnou <asmirnou@pinefeat.co.uk>
Cc: 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 0/2] Pinefeat cef168 lens control board driver
Date: Mon, 1 Jun 2026 09:59:16 +0100 [thread overview]
Message-ID: <d80db00a-42cf-4d97-93e6-de3226a89fc8@ideasonboard.com> (raw)
In-Reply-To: <20260530114643.12795-1-asmirnou@pinefeat.co.uk>
On 30/05/2026 12:46, Aliaksandr Smirnou wrote:
> On Thu, 28 May 2026 09:36:13 +0100, Alen Karnil wrote:
>
>>> Could you please ensure you are using the Makefile provided in the cef168
>>> repository?
>> ```
>> $ make
>> make -C "/lib/modules/`uname -r`/build" M="/home/admin/work/cef168"
>> DTC_INCLUDE="/usr/src/linux-headers-`uname -r | sed
>> 's/rpt-.*/rpt-common-rpi/'`/include"
>> make[1]: Entering directory '/home/admin/linux'
>> make[2]: Entering directory '/home/admin/work/cef168'
>> CC [M] cef168.o
>> make[4]: *** No rule to make target 'imx477.dtbo', needed by
>> 'modules.order'. Stop.
>> make[3]: *** [/home/admin/linux/Makefile:2024: .] Error 2
>> make[2]: *** [/home/admin/linux/Makefile:248: __sub-make] Error 2
>> make[2]: Leaving directory '/home/admin/work/cef168'
>> make[1]: *** [Makefile:248: __sub-make] Error 2
>> make[1]: Leaving directory '/home/admin/linux'
>> make: *** [Makefile:16: default] Error 2
>> ```
>>
>> This is what I got hung up on, which is why I moved onto copying the
>> .dts* and building it from the kernel directory, which lead into the
>> previous issue and me needing to roll my own .dts*
>
> Could you pull the latest version of the main branch from the cef168
> repository? This issue was fixed recently, so it looks like the code
> you pulled was from before that fix was merged.
>
> The fix involved using the dtb-y target instead of obj-m in the Makefile.
Just tested it, now it works, thanks.
>
>>> Will do. Should I update the patch before or after your review?
>>
>> I would prefer if you were to update it before just so we are in sync,
>> thank you.
>
> Will do.
I will continue the review once it's received.
prev parent reply other threads:[~2026-06-01 8:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-07 19:57 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
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 [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=d80db00a-42cf-4d97-93e6-de3226a89fc8@ideasonboard.com \
--to=alen.karnil@ideasonboard.com \
--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
Powered by JetHome