From: abhinavk@codeaurora.org
To: Stephen Boyd <swboyd@chromium.org>
Cc: dri-devel@lists.freedesktop.org,
kernel test robot <lkp@intel.com>,
linux-arm-msm@vger.kernel.org, khsieh@codeaurora.org,
seanpaul@chromium.org, tanmay@codeaurora.org,
aravindh@codeaurora.org, freedreno@lists.freedesktop.org
Subject: Re: [PATCH] drm/msm/dp: fix incorrect function prototype of dp_debug_get()
Date: Thu, 24 Sep 2020 11:06:38 -0700 [thread overview]
Message-ID: <9b14d270ac94a7b17e13a2d4ac86ffdc@codeaurora.org> (raw)
In-Reply-To: <160092913200.310579.7777419545906412437@swboyd.mtv.corp.google.com>
Hi Stephen
Thanks for the review.
On 2020-09-23 23:32, Stephen Boyd wrote:
> Quoting Abhinav Kumar (2020-09-23 16:24:48)
>> Fix the incorrect function prototype for dp_debug_get()
>> in the dp_debug module to address compilation warning.
>>
>> Fixes: f913454aae8e ("drm/msm/dp: move debugfs node to
>> /sys/kernel/debug/dri/*/")
>> Reported-by: kernel test robot <lkp@intel.com>
>> Signed-off-by: Abhinav Kumar <abhinavk@codeaurora.org>
>> ---
>
> Reviewed-by: Stephen Boyd <swboyd@chromium.org>
>
> Will the compliance testing parts be moved out of debugfs at some
> point?
> Just curious what the plan is there.
No, the video pattern compliance testing parts will remain in debugfs as
they use
IGT as the userspace entity which is debugfs based for DP compliance
tests.
> _______________________________________________
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2020-09-24 18:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-23 23:24 [PATCH] drm/msm/dp: fix incorrect function prototype of dp_debug_get() Abhinav Kumar
2020-09-24 6:32 ` Stephen Boyd
2020-09-24 18:06 ` abhinavk [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=9b14d270ac94a7b17e13a2d4ac86ffdc@codeaurora.org \
--to=abhinavk@codeaurora.org \
--cc=aravindh@codeaurora.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=khsieh@codeaurora.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=lkp@intel.com \
--cc=seanpaul@chromium.org \
--cc=swboyd@chromium.org \
--cc=tanmay@codeaurora.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