From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Jack Zhu <jack.zhu@starfivetech.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Robert Foss <rfoss@kernel.org>, Todor Tomov <todor.too@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Maxime Ripard <mripard@kernel.org>,
Philipp Zabel <p.zabel@pengutronix.de>
Cc: linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, changhuang.liang@starfivetech.com
Subject: Re: [PATCH v1 11/11] media: starfive: enable building
Date: Wed, 8 Mar 2023 12:07:49 +0100 [thread overview]
Message-ID: <efddfbf3-8003-c5e5-5054-3d30287c4b23@linaro.org> (raw)
In-Reply-To: <05465184-5976-6cee-9925-e3712a1ea650@starfivetech.com>
On 08/03/2023 12:03, Jack Zhu wrote:
>
>
> On 2023/3/8 18:33, Krzysztof Kozlowski wrote:
>> On 07/03/2023 10:46, Jack Zhu wrote:
>>>
>>>
>>> On 2023/3/3 16:43, Krzysztof Kozlowski wrote:
>>>> On 02/03/2023 10:19, jack.zhu wrote:
>>>>> Add Kconfig and Makefie, update platform/Kconfig and platform/Makefile
>>>>> to enable building of the Starfive Camera subsystem driver.
>>>>>
>>>>> Signed-off-by: jack.zhu <jack.zhu@starfivetech.com>
>>>>> ---
>>>>> drivers/media/platform/Kconfig | 1 +
>>>>> drivers/media/platform/Makefile | 1 +
>>>>> drivers/media/platform/starfive/Kconfig | 18 ++++++++++++++++++
>>>>> drivers/media/platform/starfive/Makefile | 14 ++++++++++++++
>>>>
>>>> This is not a separate commit. If it were, it would mean you just added
>>>> dead code in previous commits, so why adding dead code in first place?
>>>>
>>>
>>> The previous patches are made according to the module function.I think
>>> it is helpful to explain the composition of the code file.
>>>
>>> stf_camss[patch 9] as a platform device manages all resources including
>>> ISP and VIN. ISP/VIN [patch 7/8]as a sub-device needs to access other
>>> resources managed by stf_camss.There is mutual reference between them.
>>> Therefore, this patch is used for the overall compilation of the starfive
>>> directory.
>>
>> So previous code is dead? Again, what is the reason for adding dead
>> code? Mutual reference is not the answer.
>>
>
> Maybe I need to merge the previous patches[6-11] into one patch to submit?
I gave you the recommendation in my first reply. What's wrong with it?
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-03-08 11:08 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230302091921.43309-1-jack.zhu@starfivetech.com>
[not found] ` <20230302091921.43309-2-jack.zhu@starfivetech.com>
2023-03-03 8:34 ` [PATCH v1 01/11] media: dt-bindings: starfive,jh7110-camss: add binding document Krzysztof Kozlowski
2023-03-07 6:20 ` Jack Zhu
2023-03-03 8:35 ` Krzysztof Kozlowski
2023-03-07 6:35 ` Jack Zhu
[not found] ` <20230302091921.43309-3-jack.zhu@starfivetech.com>
2023-03-03 8:42 ` [PATCH v1 02/11] media: dt-bindings: starfive,jh7110-mipi-csi2: add binding docmuent Krzysztof Kozlowski
2023-03-03 8:47 ` Krzysztof Kozlowski
2023-03-07 6:41 ` Jack Zhu
2023-03-07 7:53 ` Krzysztof Kozlowski
2023-03-07 10:08 ` Jack Zhu
2023-03-08 10:32 ` Krzysztof Kozlowski
[not found] ` <20230302091921.43309-5-jack.zhu@starfivetech.com>
2023-03-03 8:42 ` [PATCH v1 04/11] MAINTAINERS: add Starfive Camera subsystem driver Krzysztof Kozlowski
2023-03-09 2:52 ` Jack Zhu
[not found] ` <20230302091921.43309-12-jack.zhu@starfivetech.com>
2023-03-03 8:43 ` [PATCH v1 11/11] media: starfive: enable building Krzysztof Kozlowski
2023-03-07 9:46 ` Jack Zhu
2023-03-08 10:33 ` Krzysztof Kozlowski
2023-03-08 11:03 ` Jack Zhu
2023-03-08 11:07 ` Krzysztof Kozlowski [this message]
2023-03-09 2:13 ` Jack Zhu
[not found] ` <20230302091921.43309-11-jack.zhu@starfivetech.com>
2023-03-03 8:44 ` [PATCH v1 10/11] media: uapi: add user space interfaces Krzysztof Kozlowski
2023-03-09 2:22 ` Jack Zhu
[not found] ` <20230302091921.43309-7-jack.zhu@starfivetech.com>
2023-03-03 8:45 ` [PATCH v1 06/11] media: starfive: add ISP driver files Krzysztof Kozlowski
2023-03-07 9:53 ` Jack Zhu
2023-03-08 10:34 ` Krzysztof Kozlowski
2023-03-08 11:04 ` Jack Zhu
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=efddfbf3-8003-c5e5-5054-3d30287c4b23@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=changhuang.liang@starfivetech.com \
--cc=devicetree@vger.kernel.org \
--cc=jack.zhu@starfivetech.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=mripard@kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=rfoss@kernel.org \
--cc=robh+dt@kernel.org \
--cc=todor.too@gmail.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