linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Abhinav Kumar <quic_abhinavk@quicinc.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
	Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
	Kuogee Hsieh <quic_khsieh@quicinc.com>
Cc: <devicetree@vger.kernel.org>, <quic_sbillaka@quicinc.com>,
	<freedreno@lists.freedesktop.org>,
	<krzysztof.kozlowski+dt@linaro.org>, <airlied@gmail.com>,
	<andersson@kernel.org>, <konrad.dybcio@somainline.org>,
	<robdclark@gmail.com>, <dri-devel@lists.freedesktop.org>,
	<dianders@chromium.org>, <robh+dt@kernel.org>, <vkoul@kernel.org>,
	<agross@kernel.org>, <daniel@ffwll.ch>,
	<linux-arm-msm@vger.kernel.org>, <swboyd@chromium.org>,
	<sean@poorly.run>, <linux-kernel@vger.kernel.org>
Subject: Re: [Freedreno] [PATCH v11 2/5] dt-bindings: msm/dp: add data-lanes and link-frequencies property
Date: Tue, 13 Dec 2022 09:31:44 -0800	[thread overview]
Message-ID: <0c131d43-1e91-8b92-5517-ca8fffef238c@quicinc.com> (raw)
In-Reply-To: <bca77270-f3ac-f23f-ef96-43f9f7d574c4@linaro.org>



On 12/13/2022 5:13 AM, Krzysztof Kozlowski wrote:
> On 13/12/2022 00:41, Abhinav Kumar wrote:
>>>>
>>>> besides, i think i have to sent the whole series patches include this
>>>> one to address your new comments on other patch.
>>>>
>>>> is this correct?
>>>
>>> No. Please fix your system first, validate your patches and send them
>>> afterwards. You can not expect others to do your job.
>>>
>>
>> Just finished working with kuogee on this. This issue had been reported
>> by few others earlier (example
>> https://lore.kernel.org/lkml/bc9be279-a130-d5e7-4397-bbb389d14403@intel.com/T/).
> 
> This report says:
> "Sorry for the inconvenience, please ignore this false positive."
> 

That was one of them, and I dont think its false, maybe because after 
fixing the PATH issues, the user deemed them as false.

Here is another one 
https://patchwork.ozlabs.org/project/devicetree-bindings/patch/20210812174209.1970-3-bbudiredla@marvell.com/ 
with the same report but no resolution.

So i thought for the benefit of others I would atleast summarize how we 
resolved them.

> Best regards,
> Krzysztof
> 

  reply	other threads:[~2022-12-13 17:32 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-08 22:36 [PATCH v11 0/5] Add data-lanes and link-frequencies to dp_out endpoint Kuogee Hsieh
2022-12-08 22:36 ` [PATCH v11 1/5] arm64: dts: qcom: add data-lanes and link-freuencies into " Kuogee Hsieh
2022-12-09 14:57   ` Krzysztof Kozlowski
2022-12-08 22:36 ` [PATCH v11 2/5] dt-bindings: msm/dp: add data-lanes and link-frequencies property Kuogee Hsieh
2022-12-08 23:33   ` Dmitry Baryshkov
2022-12-08 23:38     ` Kuogee Hsieh
2022-12-09  0:11       ` Dmitry Baryshkov
2022-12-09  0:22         ` Kuogee Hsieh
2022-12-09  0:35           ` Dmitry Baryshkov
2022-12-12 17:51             ` Kuogee Hsieh
2022-12-12 22:35               ` Dmitry Baryshkov
2022-12-12 23:41                 ` Abhinav Kumar
2022-12-13  1:02                   ` Dmitry Baryshkov
2022-12-13 13:13                   ` Krzysztof Kozlowski
2022-12-13 17:31                     ` Abhinav Kumar [this message]
2022-12-13 19:22                       ` [Freedreno] " Krzysztof Kozlowski
2022-12-09 14:59       ` Krzysztof Kozlowski
2022-12-09 12:14   ` Rob Herring
2022-12-08 22:36 ` [PATCH v11 3/5] drm/msm/dp: parser data-lanes as property of dp_out endpoint Kuogee Hsieh
2022-12-08 22:36 ` [PATCH v11 4/5] drm/msm/dp: parser link-frequencies " Kuogee Hsieh
2022-12-08 23:17   ` Dmitry Baryshkov
2022-12-10  3:57   ` kernel test robot
2022-12-08 22:36 ` [PATCH v11 5/5] drm/msm/dp: add support of max dp link rate Kuogee Hsieh

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=0c131d43-1e91-8b92-5517-ca8fffef238c@quicinc.com \
    --to=quic_abhinavk@quicinc.com \
    --cc=agross@kernel.org \
    --cc=airlied@gmail.com \
    --cc=andersson@kernel.org \
    --cc=daniel@ffwll.ch \
    --cc=devicetree@vger.kernel.org \
    --cc=dianders@chromium.org \
    --cc=dmitry.baryshkov@linaro.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=freedreno@lists.freedesktop.org \
    --cc=konrad.dybcio@somainline.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=quic_khsieh@quicinc.com \
    --cc=quic_sbillaka@quicinc.com \
    --cc=robdclark@gmail.com \
    --cc=robh+dt@kernel.org \
    --cc=sean@poorly.run \
    --cc=swboyd@chromium.org \
    --cc=vkoul@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;
as well as URLs for NNTP newsgroup(s).