public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Mukesh Kumar Savaliya <quic_msavaliy@quicinc.com>,
	alexandre.belloni@bootlin.com, robh@kernel.org,
	krzk+dt@kernel.org, conor+dt@kernel.org,
	jarkko.nikula@linux.intel.com, linux-i3c@lists.infradead.org,
	linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Trilok Soni <quic_tsoni@quicinc.com>
Cc: andersson@kernel.org, konradybcio@kernel.org
Subject: Re: [PATCH v2 2/3] i3c: master: Add Qualcomm I3C controller driver
Date: Wed, 26 Mar 2025 15:28:07 +0100	[thread overview]
Message-ID: <d0b178ab-ad22-4230-a790-6a19a6abfd89@kernel.org> (raw)
In-Reply-To: <20250326141641.3471906-3-quic_msavaliy@quicinc.com>

On 26/03/2025 15:16, Mukesh Kumar Savaliya wrote:
> +
> +static int i3c_geni_resources_init(struct geni_i3c_dev *gi3c, struct platform_device *pdev)
> +{
> +	int ret;
> +
> +	gi3c->se.base = devm_platform_ioremap_resource(pdev, 0);
> +	if (IS_ERR(gi3c->se.base))
> +		return PTR_ERR(gi3c->se.base);
> +
> +	gi3c->se.clk = devm_clk_get(&pdev->dev, "se-clk");

Never tested.

> +	if (IS_ERR(gi3c->se.clk))
> +		return dev_err_probe(&pdev->dev, PTR_ERR(gi3c->se.clk),
> +							"Unable to get serial engine core clock: %pe\n",
> +							gi3c->se.clk);
> +
> +	ret = device_property_read_u32(&pdev->dev, "se-clock-frequency", &gi3c->clk_src_freq);

I don't see previous comments implemented. Comment was: "Drop".

You did not test the DTS - again - even though I asked for that.

You claim you did internal review, but I have doubts because internal
review would tell you how to test it (there is comprehensive internal
guide - see go/upstream). Then the testing would point out this issue.

Such trivial things should not be in v1 even. But they happened so you
got the review. Now you sent v2 ignoring that public review.

Sorry guys, please improve internal processes instead of wasting
reviewers time.

NAK.

Best regards,
Krzysztof

  reply	other threads:[~2025-03-26 14:28 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-26 14:16 [PATCH v2 0/3] Add Qualcomm i3c master controller driver support Mukesh Kumar Savaliya
2025-03-26 14:16 ` [PATCH v2 1/3] dt-bindings: i3c: Add Qualcomm I3C master controller Mukesh Kumar Savaliya
2025-03-26 14:23   ` Krzysztof Kozlowski
2025-03-28 14:28     ` Mukesh Kumar Savaliya
2025-03-28 14:33       ` Krzysztof Kozlowski
2025-03-29  9:08         ` Mukesh Kumar Savaliya
2025-03-29 11:06           ` Krzysztof Kozlowski
2025-03-29 14:31             ` Mukesh Kumar Savaliya
2025-03-30  9:42               ` Krzysztof Kozlowski
2025-03-31  6:52                 ` Mukesh Kumar Savaliya
2025-03-31  7:06                   ` Mukesh Kumar Savaliya
2025-03-26 14:16 ` [PATCH v2 2/3] i3c: master: Add Qualcomm I3C controller driver Mukesh Kumar Savaliya
2025-03-26 14:28   ` Krzysztof Kozlowski [this message]
2025-03-28 14:28     ` Mukesh Kumar Savaliya
2025-03-28 14:35       ` Krzysztof Kozlowski
2025-03-26 20:03   ` Frank Li
2025-03-29  9:09     ` Mukesh Kumar Savaliya
2025-03-28 13:19   ` Markus Elfring
2025-03-28 14:29     ` Mukesh Kumar Savaliya
2025-03-28 19:04       ` [v2 " Markus Elfring
2025-03-29  9:08         ` Mukesh Kumar Savaliya
2025-03-29  9:43           ` Markus Elfring
2025-03-29 10:48           ` Alexandre Belloni
2025-03-29 13:16             ` Markus Elfring
2025-03-29 14:27             ` Mukesh Kumar Savaliya
2025-03-28 13:28   ` [PATCH v2 " Markus Elfring
2025-03-28 14:29     ` Mukesh Kumar Savaliya
2025-03-26 14:16 ` [PATCH v2 3/3] MAINTAINERS: Add maintainer for Qualcomm's I3C driver Mukesh Kumar Savaliya

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=d0b178ab-ad22-4230-a790-6a19a6abfd89@kernel.org \
    --to=krzk@kernel.org \
    --cc=alexandre.belloni@bootlin.com \
    --cc=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=jarkko.nikula@linux.intel.com \
    --cc=konradybcio@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-i3c@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=quic_msavaliy@quicinc.com \
    --cc=quic_tsoni@quicinc.com \
    --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