From: Boris Brezillon <boris.brezillon@bootlin.com>
To: David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>,
dri-devel@lists.freedesktop.org
Cc: Liviu Dudau <Liviu.Dudau@arm.com>
Subject: Re: [PATCH] drm/writeback: Fix the "overview" section of the doc
Date: Tue, 3 Jul 2018 21:45:24 +0200 [thread overview]
Message-ID: <20180703214524.67836ac3@bbrezillon> (raw)
In-Reply-To: <20180703194400.273c6fe2@bbrezillon>
On Tue, 3 Jul 2018 19:44:00 +0200
Boris Brezillon <boris.brezillon@bootlin.com> wrote:
> On Tue, 3 Jul 2018 19:40:46 +0200
> Boris Brezillon <boris.brezillon@bootlin.com> wrote:
>
> > Fix the bullet list declaration in the overview section.
> >
> > Signed-off-by: Boris Brezillon <boris.brezillon@bootlin.com>
>
> Forgot to add:
>
> Reported-by: Daniel Vetter <daniel.vetter@ffwll.ch>
And
Fixes: 935774cd71fe ("drm: Add writeback connector type")
is missing too.
>
> > ---
> > drivers/gpu/drm/drm_writeback.c | 11 +++++++----
> > 1 file changed, 7 insertions(+), 4 deletions(-)
> >
> > diff --git a/drivers/gpu/drm/drm_writeback.c b/drivers/gpu/drm/drm_writeback.c
> > index 827395071f0b..69e7a63cfcc3 100644
> > --- a/drivers/gpu/drm/drm_writeback.c
> > +++ b/drivers/gpu/drm/drm_writeback.c
> > @@ -22,10 +22,13 @@
> > * Writeback connectors are used to expose hardware which can write the output
> > * from a CRTC to a memory buffer. They are used and act similarly to other
> > * types of connectors, with some important differences:
> > - * - Writeback connectors don't provide a way to output visually to the user.
> > - * - Writeback connectors should always report as "disconnected" (so that
> > - * clients which don't understand them will ignore them).
> > - * - Writeback connectors don't have EDID.
> > + *
> > + * * Writeback connectors don't provide a way to output visually to the user.
> > + *
> > + * * Writeback connectors should always report as "disconnected" (so that
> > + * clients which don't understand them will ignore them).
> > + *
> > + * * Writeback connectors don't have EDID.
> > *
> > * A framebuffer may only be attached to a writeback connector when the
> > * connector is attached to a CRTC. The WRITEBACK_FB_ID property which sets the
>
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2018-07-03 19:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-03 17:40 [PATCH] drm/writeback: Fix the "overview" section of the doc Boris Brezillon
2018-07-03 17:44 ` Boris Brezillon
2018-07-03 19:45 ` Boris Brezillon [this message]
2018-07-04 8:32 ` Daniel Vetter
2018-07-07 6:24 ` Boris Brezillon
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=20180703214524.67836ac3@bbrezillon \
--to=boris.brezillon@bootlin.com \
--cc=Liviu.Dudau@arm.com \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.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