From: Jani Nikula <jani.nikula@linux.intel.com>
To: "Souza, Jose" <jose.souza@intel.com>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"Pandiyan, Dhinakaran" <dhinakaran.pandiyan@intel.com>
Cc: "dri-devel@lists.freedesktop.org" <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH] drm: Fix documentation generation for DP_DPCD_QUIRK_NO_PSR
Date: Wed, 19 Dec 2018 15:59:34 +0200 [thread overview]
Message-ID: <87o99hvcqh.fsf@intel.com> (raw)
In-Reply-To: <52c3817f779e6b555bd4f3182ad6f3ab48126c02.camel@intel.com>
On Thu, 06 Dec 2018, "Souza, Jose" <jose.souza@intel.com> wrote:
> On Wed, 2018-12-05 at 12:30 -0800, Dhinakaran Pandiyan wrote:
>> On Wed, 2018-12-05 at 10:48 -0800, José Roberto de Souza wrote:
>> > The DP_DPCD_QUIRK_NO_PSR comment is missing colon causing this
>> > warning when generating kernel documentation.
>> >
>> > ./include/drm/drm_dp_helper.h:1374: warning: Incorrect use of
>> > kernel-
>> > doc format: * @DP_DPCD_QUIRK_NO_PSR
>> >
>> Cc: dri-devel@lists.freedesktop.org
>> Reviewed-by: Dhinakaran Pandiyan <dhinakaran.pandiyan@intel.com>
>
> Thanks for the review, merged.
This patch is not i915 specific, and should have been merged via
drm-misc intead of drm-intel.
dim will have told you this when you applied the patch to dinq:
---
The following files are outside of i915 maintenance scope:
include/drm/drm_dp_helper.h
Confirm you have appropriate Acked-by and Reviewed-by for above files.
---
As a reminder, you need specific acks to merge non-i915 changes through
drm-intel, and that's reserved for special cases.
Please pay more attention to the maintenance boundaries going forward.
Thanks,
Jani.
>
>> > Fixes: 7c5c641a930e (drm/i915: Disable PSR in Apple panels)
>> > Cc: Dhinakaran Pandiyan <dhinakaran.pandiyan@intel.com>
>> > Signed-off-by: José Roberto de Souza <jose.souza@intel.com>
>> > ---
>> > include/drm/drm_dp_helper.h | 2 +-
>> > 1 file changed, 1 insertion(+), 1 deletion(-)
>> >
>> > diff --git a/include/drm/drm_dp_helper.h
>> > b/include/drm/drm_dp_helper.h
>> > index 18cfde45b8ed..c223c87ef119 100644
>> > --- a/include/drm/drm_dp_helper.h
>> > +++ b/include/drm/drm_dp_helper.h
>> > @@ -1370,7 +1370,7 @@ enum drm_dp_quirk {
>> > */
>> > DP_DPCD_QUIRK_CONSTANT_N,
>> > /**
>> > - * @DP_DPCD_QUIRK_NO_PSR
>> > + * @DP_DPCD_QUIRK_NO_PSR:
>> > *
>> > * The device does not support PSR even if reports that it
>> > supports or
>> > * driver still need to implement proper handling for such
>> > device.
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/intel-gfx
--
Jani Nikula, Intel Open Source Graphics Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2018-12-19 13:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-05 18:48 [PATCH] drm: Fix documentation generation for DP_DPCD_QUIRK_NO_PSR José Roberto de Souza
2018-12-05 19:23 ` ✓ Fi.CI.BAT: success for " Patchwork
2018-12-05 20:30 ` [PATCH] " Dhinakaran Pandiyan
2018-12-06 1:14 ` Souza, Jose
2018-12-19 13:59 ` Jani Nikula [this message]
2018-12-06 1:04 ` ✓ Fi.CI.IGT: success for " Patchwork
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=87o99hvcqh.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=dhinakaran.pandiyan@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jose.souza@intel.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;
as well as URLs for NNTP newsgroup(s).