From: Doug Anderson <dianders@chromium.org>
To: Thierry Reding <thierry.reding@gmail.com>,
Sam Ravnborg <sam@ravnborg.org>
Cc: David Airlie <airlied@linux.ie>,
dri-devel <dri-devel@lists.freedesktop.org>,
Daniel Vetter <daniel@ffwll.ch>, Rob Herring <robh+dt@kernel.org>,
Rob Clark <robdclark@chromium.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v4 1/5] drm: panel: simple: Fixup the struct panel_desc kernel doc
Date: Mon, 23 Nov 2020 09:24:50 -0800 [thread overview]
Message-ID: <CAD=FV=WEL8OyZLGrdVz54XaHS-56D8zbKyN2ZZcnPMsHezPrbQ@mail.gmail.com> (raw)
In-Reply-To: <20201109170018.v4.1.Icaa86f0a4ca45a9a7184da4bc63386b29792d613@changeid>
Hi,
On Mon, Nov 9, 2020 at 5:01 PM Douglas Anderson <dianders@chromium.org> wrote:
>
> When I run:
> scripts/kernel-doc -rst drivers/gpu/drm/panel/panel-simple.c
>
> I see that several of the kernel-doc entries aren't showing up because
> they don't specify the full path down the hierarchy. Let's fix that
> and also move to inline kernel docs.
>
> Signed-off-by: Douglas Anderson <dianders@chromium.org>
> ---
>
> Changes in v4:
> - ("drm: panel: simple: Fixup the struct panel_desc kernel doc") new for v4.
>
> drivers/gpu/drm/panel/panel-simple.c | 59 ++++++++++++++++++++--------
> 1 file changed, 42 insertions(+), 17 deletions(-)
I'm curious if there are any outstanding actions I need to take for
this series. I know I found that on patch #4 I should have added the
sync flags [1] but I was waiting to see if there was any other
feedback before sending a v5. If there's nothing else I'm happy with
any of:
a) I can send a v5 with that small fix.
b) v4 can land an the maintainer landing can add the ".flags =
DRM_MODE_FLAG_PHSYNC | DRM_MODE_FLAG_NVSYNC," into the patch when
landing.
c) v4 can land and I can send a follow-up patch with the sync flags fix.
I know it's the holidays right now and folks are busy, but I just
wanted to see if there were any actions I needed to take. Personally
I'm on vacation the last 3 days this week and I imagine I'll come back
to work Monday swamped with email, so today/tomorrow would be an ideal
time to send a spin if one is needed. Thanks!
-Doug
[1] https://lore.kernel.org/r/CAD=FV=UPkuJ5E2sCQeozNR3CO+LZW=DW9h77vfooeiSMqGnYpA@mail.gmail.com
next prev parent reply other threads:[~2020-11-23 17:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-10 1:00 [PATCH v4 1/5] drm: panel: simple: Fixup the struct panel_desc kernel doc Douglas Anderson
2020-11-10 1:00 ` [PATCH v4 2/5] drm: panel: simple: Defer unprepare delay till next prepare to shorten it Douglas Anderson
2020-11-29 22:11 ` Sam Ravnborg
2020-11-10 1:00 ` [PATCH v4 3/5] drm: panel: simple: Allow specifying the delay from prepare to enable Douglas Anderson
2020-11-29 22:11 ` Sam Ravnborg
2020-11-10 1:00 ` [PATCH v4 4/5] drm: panel: simple: Add BOE NV110WTM-N61 Douglas Anderson
2020-11-10 2:32 ` Doug Anderson
2020-11-29 22:12 ` Sam Ravnborg
2020-11-10 1:00 ` [PATCH v4 5/5] dt-bindings: dt-bindings: display: " Douglas Anderson
2020-11-23 17:24 ` Doug Anderson [this message]
2020-11-29 22:10 ` [PATCH v4 1/5] drm: panel: simple: Fixup the struct panel_desc kernel doc Sam Ravnborg
2020-12-01 21:00 ` Doug Anderson
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='CAD=FV=WEL8OyZLGrdVz54XaHS-56D8zbKyN2ZZcnPMsHezPrbQ@mail.gmail.com' \
--to=dianders@chromium.org \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robdclark@chromium.org \
--cc=robh+dt@kernel.org \
--cc=sam@ravnborg.org \
--cc=thierry.reding@gmail.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).