From: Daniel Vetter <daniel@ffwll.ch>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
Lubomir Rintel <lkundrak@v3.sk>,
DRI Development <dri-devel@lists.freedesktop.org>,
Daniel Vetter <daniel.vetter@intel.com>
Subject: Re: [PATCH 4/5] drm/doc: Move bridge link target to the right place
Date: Sat, 12 Jan 2019 13:08:42 +0100 [thread overview]
Message-ID: <20190112120842.GJ21184@phenom.ffwll.local> (raw)
In-Reply-To: <20190111223639.GD25215@ravnborg.org>
On Fri, Jan 11, 2019 at 11:36:39PM +0100, Sam Ravnborg wrote:
> On Fri, Jan 11, 2019 at 05:40:47PM +0100, Daniel Vetter wrote:
> > I screwed up a rebase somehow.
> >
> > v2: Drop bogus hunk.
> >
> > v3: Really drop bogus hunk (Lubomir).
> >
> > Cc: Lubomir Rintel <lkundrak@v3.sk>
> > Signed-off-by: Daniel Vetter <daniel.vetter@intel.com>
> Reviewed-by: Sam Ravnborg <sam@ravnborg.org>
Thanks a lot for your review, all remaining patches applied to
drm-misc-next.
-Daniel
--
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
next prev parent reply other threads:[~2019-01-12 12:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-11 16:40 [PATCH 1/5] drm/docs: improve docs for drm_drv.c Daniel Vetter
2019-01-11 16:40 ` [PATCH 2/5] drm/of: Fix kerneldoc Daniel Vetter
2019-01-11 22:35 ` Sam Ravnborg
2019-01-11 16:40 ` [PATCH 3/5] drm/panel: Small documentation polish Daniel Vetter
2019-01-11 22:36 ` Sam Ravnborg
2019-01-11 16:40 ` [PATCH 4/5] drm/doc: Move bridge link target to the right place Daniel Vetter
2019-01-11 22:36 ` Sam Ravnborg
2019-01-12 12:08 ` Daniel Vetter [this message]
2019-01-11 16:40 ` [PATCH 5/5] drm/doc: Polish kerneldoc for drm_device.h Daniel Vetter
2019-01-11 17:15 ` Sam Ravnborg
2019-01-11 22:20 ` Daniel Vetter
2019-01-11 22:35 ` [PATCH 1/5] drm/docs: improve docs for drm_drv.c Sam Ravnborg
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=20190112120842.GJ21184@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=daniel.vetter@ffwll.ch \
--cc=daniel.vetter@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=lkundrak@v3.sk \
--cc=sam@ravnborg.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