From: Krzysztof Kozlowski <krzk@kernel.org>
To: kernel test robot <lkp@intel.com>,
Jagadeesh Kona <quic_jkona@quicinc.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>,
Bjorn Andersson <andersson@kernel.org>,
Bryan O'Donoghue <bryan.odonoghue@linaro.org>,
Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
Vladimir Zapolskiy <vladimir.zapolskiy@linaro.org>
Subject: Re: [linux-next:master 7766/10451] drivers/clk/qcom/camcc-sm8650.c:3573:29: error: incompatible pointer types passing 'struct device *' to parameter of type 'struct platform_device *'
Date: Thu, 18 Jul 2024 08:48:43 +0200 [thread overview]
Message-ID: <edfd90b7-b94b-4b1d-a625-a240a8446f1e@kernel.org> (raw)
In-Reply-To: <202407072331.baglL4Sd-lkp@intel.com>
On 07/07/2024 17:20, kernel test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> head: 0b58e108042b0ed28a71cd7edf5175999955b233
> commit: 09ea421652a832083ea380a72addf383965f3682 [7766/10451] clk: qcom: camcc-sm8650: Add SM8650 camera clock controller driver
> config: x86_64-allyesconfig (https://download.01.org/0day-ci/archive/20240707/202407072331.baglL4Sd-lkp@intel.com/config)
> compiler: clang version 18.1.5 (https://github.com/llvm/llvm-project 617a15a9eac96088ae5e9134248d8236e34b91b1)
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240707/202407072331.baglL4Sd-lkp@intel.com/reproduce)
This and this:
https://lore.kernel.org/all/202407072212.WptVaUDt-lkp@intel.com/
are reports on linux-next. They were addressed to you/
Jagadeesh, how did you respond to public reports that your commit has
build failures in linux-next?
It reached now Linus' tree causing huge rant, unfortunately not in the
direction we would like that rant to go.
If you receive a report that your code does not even compile, it is YOUR
DAMN MOST IMPORTANT TASK to address it IMMEDIATELY.
I don't think such code should be ever accepted if contributors do not
take responsibility for their commits.
Krzysztof
>
> If you fix the issue in a separate patch/commit (i.e. not just a new version of
> the same patch/commit), kindly add following tags
> | Reported-by: kernel test robot <lkp@intel.com>
> | Closes: https://lore.kernel.org/oe-kbuild-all/202407072331.baglL4Sd-lkp@intel.com/
>
> Note: the linux-next/master HEAD 0b58e108042b0ed28a71cd7edf5175999955b233 builds fine.
> It may have been fixed somewhere.
>
> All errors (new ones prefixed by >>):
>
>>> drivers/clk/qcom/camcc-sm8650.c:3573:29: error: incompatible pointer types passing 'struct device *' to parameter of type 'struct platform_device *' [-Werror,-Wincompatible-pointer-types]
> 3573 | ret = qcom_cc_really_probe(&pdev->dev, &cam_cc_sm8650_desc, regmap);
> | ^~~~~~~~~~
> drivers/clk/qcom/common.h:63:57: note: passing argument to parameter 'pdev' here
> 63 | extern int qcom_cc_really_probe(struct platform_device *pdev,
> | ^
> 1 error generated.
>
next prev parent reply other threads:[~2024-07-18 6:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-07 15:20 kernel test robot
2024-07-18 6:48 ` Krzysztof Kozlowski [this message]
2024-07-18 9:48 ` Jagadeesh Kona
2024-07-18 10:06 ` Krzysztof Kozlowski
2024-07-19 7:06 ` Jagadeesh Kona
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=edfd90b7-b94b-4b1d-a625-a240a8446f1e@kernel.org \
--to=krzk@kernel.org \
--cc=andersson@kernel.org \
--cc=bryan.odonoghue@linaro.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=quic_jkona@quicinc.com \
--cc=vladimir.zapolskiy@linaro.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