public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Marius Vlad <marius.c.vlad@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH i-g-t 0/2] Improve remaining documentation for igt_kms
Date: Thu, 7 Jan 2016 15:29:28 +0100	[thread overview]
Message-ID: <20160107142928.GP8076@phenom.ffwll.local> (raw)
In-Reply-To: <1452175809-8161-1-git-send-email-marius.c.vlad@intel.com>

On Thu, Jan 07, 2016 at 04:10:07PM +0200, Marius Vlad wrote:
> 
> 

When resending pls write some indication of what changed, both in the over
and in the patches themselves. In the patches we do a more formal
changelog even, with a per-change v2: heading.

Also when resending the entire series please start a new thread.

Thanks, Daniel

> Marius Vlad (2):
>   lib/igt_kms: Improve documentation.
>   lib/igt_kms: Short description between Intel/DRM terminology.
> 
>  lib/igt_kms.c | 242 ++++++++++++++++++++++++++++++++++++++++++++++++----------
>  lib/igt_kms.h | 123 +++++++++++++++++++++++++++--
>  2 files changed, 318 insertions(+), 47 deletions(-)
> 
> -- 
> 2.6.2
> 

-- 
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

      parent reply	other threads:[~2016-01-07 14:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1450696045-6405-1-git-send-email-marius.c.vlad@intel.com>
     [not found] ` <1450696045-6405-2-git-send-email-marius.c.vlad@intel.com>
2015-12-21 16:09   ` [PATCH i-g-t 1/3] lib/igt_kms migrate existing documentation to header file Daniel Vetter
2015-12-22 10:05     ` Marius Vlad
2015-12-22 10:20       ` Daniel Vetter
2015-12-22 10:55         ` Marius Vlad
     [not found] ` <1452175809-8161-1-git-send-email-marius.c.vlad@intel.com>
2016-01-07 14:29   ` Daniel Vetter [this message]

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=20160107142928.GP8076@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=marius.c.vlad@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