* [PATCH] drm/writeback: Fix the "overview" section of the doc
@ 2018-07-03 17:40 Boris Brezillon
2018-07-03 17:44 ` Boris Brezillon
2018-07-07 6:24 ` Boris Brezillon
0 siblings, 2 replies; 5+ messages in thread
From: Boris Brezillon @ 2018-07-03 17:40 UTC (permalink / raw)
To: David Airlie, Daniel Vetter, dri-devel; +Cc: Boris Brezillon, Liviu Dudau
Fix the bullet list declaration in the overview section.
Signed-off-by: Boris Brezillon <boris.brezillon@bootlin.com>
---
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
--
2.14.1
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
^ permalink raw reply related [flat|nested] 5+ messages in thread
* Re: [PATCH] drm/writeback: Fix the "overview" section of the doc
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
2018-07-07 6:24 ` Boris Brezillon
1 sibling, 1 reply; 5+ messages in thread
From: Boris Brezillon @ 2018-07-03 17:44 UTC (permalink / raw)
To: David Airlie, Daniel Vetter, dri-devel; +Cc: Liviu Dudau
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>
> ---
> 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
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [PATCH] drm/writeback: Fix the "overview" section of the doc
2018-07-03 17:44 ` Boris Brezillon
@ 2018-07-03 19:45 ` Boris Brezillon
2018-07-04 8:32 ` Daniel Vetter
0 siblings, 1 reply; 5+ messages in thread
From: Boris Brezillon @ 2018-07-03 19:45 UTC (permalink / raw)
To: David Airlie, Daniel Vetter, dri-devel; +Cc: Liviu Dudau
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
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [PATCH] drm/writeback: Fix the "overview" section of the doc
2018-07-03 19:45 ` Boris Brezillon
@ 2018-07-04 8:32 ` Daniel Vetter
0 siblings, 0 replies; 5+ messages in thread
From: Daniel Vetter @ 2018-07-04 8:32 UTC (permalink / raw)
To: Boris Brezillon; +Cc: David Airlie, Liviu Dudau, dri-devel
On Tue, Jul 03, 2018 at 09:45:24PM +0200, Boris Brezillon wrote:
> 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.
Acked-by: Daniel Vetter <daniel.vetter@ffwll.ch>
Thanks for the quick fix.
-Daniel
>
> >
> > > ---
> > > 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
> >
>
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [PATCH] drm/writeback: Fix the "overview" section of the doc
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-07 6:24 ` Boris Brezillon
1 sibling, 0 replies; 5+ messages in thread
From: Boris Brezillon @ 2018-07-07 6:24 UTC (permalink / raw)
To: David Airlie, Daniel Vetter, dri-devel; +Cc: Liviu Dudau
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>
Applied to drm-misc-next.
> ---
> 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
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2018-07-07 6:24 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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
2018-07-04 8:32 ` Daniel Vetter
2018-07-07 6:24 ` Boris Brezillon
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).