[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <7z6t4sudgits372e26f37gydfxxonsduiajurr7ztgvmh3crch@mbeb66xwin5s>
Date: Wed, 6 Sep 2023 13:35:37 +0200
From: Maxime Ripard <mripard@...nel.org>
To: Sarah Walker <sarah.walker@...tec.com>
Cc: dri-devel@...ts.freedesktop.org, frank.binns@...tec.com,
donald.robson@...tec.com, boris.brezillon@...labora.com,
airlied@...il.com, daniel@...ll.ch, robh+dt@...nel.org,
krzysztof.kozlowski+dt@...aro.org, conor+dt@...nel.org,
maarten.lankhorst@...ux.intel.com, tzimmermann@...e.de,
corbet@....net, christian.koenig@....com, linus.walleij@...aro.org,
matt.coster@...tec.com, linux-kernel@...r.kernel.org,
devicetree@...r.kernel.org, linux-doc@...r.kernel.org,
faith.ekstrand@...labora.com, afd@...com, hns@...delico.com,
matthew.brost@...el.com, luben.tuikov@....com, dakr@...hat.com
Subject: Re: [PATCH v6 02/20] drm/gpuva_mgr: Helper to get range of unmap
from a remap op.
Hi Sarah,
On Wed, Sep 06, 2023 at 10:55:24AM +0100, Sarah Walker wrote:
> From: Donald Robson <donald.robson@...tec.com>
>
> Signed-off-by: Donald Robson <donald.robson@...tec.com>
Sorry, this applied to your previous versions too but I only caught it
right now. When you submit a patch on someone else's behalf, you need to
add your Signed-off-by. That's also true when you're the committer of a
patch you didn't write.
This one, and patch 1, are affected.
Also, generally speaking, it's a good to write a commit log for a patch
to at least provide some context on what you want to achieve.
Maxime
Download attachment "signature.asc" of type "application/pgp-signature" (229 bytes)
Powered by blists - more mailing lists