All of lore.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <k.kozlowski@samsung.com>
To: Benjamin Gaignard <benjamin.gaignard@linaro.org>
Cc: linux-samsung-soc@vger.kernel.org,
	Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
	Seung-Woo Kim <sw0312.kim@samsung.com>,
	"dri-devel@lists.freedesktop.org"
	<dri-devel@lists.freedesktop.org>,
	Andrzej Hajda <a.hajda@samsung.com>,
	Tobias Jakobi <tjakobi@math.uni-bielefeld.de>,
	Fabien Dessenne <fabien.dessenne@st.com>,
	Vincent Abriou <vincent.abriou@st.com>,
	Marek Szyprowski <m.szyprowski@samsung.com>
Subject: Re: [PATCH 3/4] drm/exynos: use generic code for managing zpos plane property
Date: Wed, 11 May 2016 14:16:34 +0200	[thread overview]
Message-ID: <573322A2.5050603@samsung.com> (raw)
In-Reply-To: <CA+M3ks7JptQqptmZNn7Xd74_=Rt2wUVauewkpez71tBFnKSEWQ@mail.gmail.com>

On 05/11/2016 02:09 PM, Benjamin Gaignard wrote:
> I haven't double check but I had to do changes into the original patch
> so I guess that "from" field comes the new commit.
> 
> I will manually edit the commit for v2,

Git keeps original author untouched. You have to manually change the
author to remove the original one (or use non-standard way of applying
patches). If you use Git, just stick to typical workflow - git am, git
commit --amend --signoff, git format-patch, etc.

Best regards,
Krzysztof
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2016-05-11 12:16 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-11 10:25 [PATCH 1/4] drm: add generic zpos property Benjamin Gaignard
2016-05-11 10:25 ` [PATCH 2/4] drm: sti: use generic zpos for plane Benjamin Gaignard
2016-05-11 10:25 ` [PATCH 3/4] drm/exynos: use generic code for managing zpos plane property Benjamin Gaignard
2016-05-11 11:54   ` Krzysztof Kozlowski
2016-05-11 12:09     ` Benjamin Gaignard
2016-05-11 12:16       ` Krzysztof Kozlowski [this message]
2016-05-11 12:26         ` Javier Martinez Canillas
2016-05-11 10:25 ` [PATCH 4/4] drm: rcar: " Benjamin Gaignard
2016-05-11 10:49   ` Laurent Pinchart
2016-05-11 11:24 ` [PATCH 1/4] drm: add generic zpos property Laurent Pinchart
2016-05-11 12:05   ` Benjamin Gaignard
2016-05-11 13:02     ` Laurent Pinchart
2016-05-11 11:56 ` Krzysztof Kozlowski
2016-05-11 13:21 ` Daniel Vetter
  -- strict thread matches above, loose matches on Subject: below --
2016-05-11 12:31 Benjamin Gaignard
2016-05-11 12:31 ` [PATCH 3/4] drm/exynos: use generic code for managing zpos plane property Benjamin Gaignard
2016-05-11 12:52   ` Krzysztof Kozlowski
2016-05-12 10:28 [PATCH 1/4] drm: add generic zpos property Benjamin Gaignard
2016-05-12 10:28 ` [PATCH 3/4] drm/exynos: use generic code for managing zpos plane property Benjamin Gaignard

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=573322A2.5050603@samsung.com \
    --to=k.kozlowski@samsung.com \
    --cc=a.hajda@samsung.com \
    --cc=b.zolnierkie@samsung.com \
    --cc=benjamin.gaignard@linaro.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=fabien.dessenne@st.com \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=m.szyprowski@samsung.com \
    --cc=sw0312.kim@samsung.com \
    --cc=tjakobi@math.uni-bielefeld.de \
    --cc=vincent.abriou@st.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.