[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3aa9ad51c2a157f9256e908152ea2545a543a15f.camel@imgtec.com>
Date: Wed, 6 Sep 2023 11:46:59 +0000
From: Sarah Walker <Sarah.Walker@...tec.com>
To: "mripard@...nel.org" <mripard@...nel.org>
CC: "corbet@....net" <corbet@....net>,
"luben.tuikov@....com" <luben.tuikov@....com>,
"christian.koenig@....com" <christian.koenig@....com>,
"krzysztof.kozlowski+dt@...aro.org"
<krzysztof.kozlowski+dt@...aro.org>,
"tzimmermann@...e.de" <tzimmermann@...e.de>,
"hns@...delico.com" <hns@...delico.com>,
"matthew.brost@...el.com" <matthew.brost@...el.com>,
"daniel@...ll.ch" <daniel@...ll.ch>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Matt Coster <Matt.Coster@...tec.com>,
"dri-devel@...ts.freedesktop.org" <dri-devel@...ts.freedesktop.org>,
"boris.brezillon@...labora.com" <boris.brezillon@...labora.com>,
"maarten.lankhorst@...ux.intel.com"
<maarten.lankhorst@...ux.intel.com>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
"linus.walleij@...aro.org" <linus.walleij@...aro.org>,
"conor+dt@...nel.org" <conor+dt@...nel.org>,
"linux-doc@...r.kernel.org" <linux-doc@...r.kernel.org>,
Frank Binns <Frank.Binns@...tec.com>,
"robh+dt@...nel.org" <robh+dt@...nel.org>,
"dakr@...hat.com" <dakr@...hat.com>,
"airlied@...il.com" <airlied@...il.com>,
Donald Robson <Donald.Robson@...tec.com>,
"faith.ekstrand@...labora.com" <faith.ekstrand@...labora.com>,
"afd@...com" <afd@...com>
Subject: Re: [PATCH v6 02/20] drm/gpuva_mgr: Helper to get range of unmap from
a remap op.
On Wed, 2023-09-06 at 13:35 +0200, Maxime Ripard wrote:
> 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.
Sorry for this, will get these issues addressed before the next patchset.
Sarah
Powered by blists - more mailing lists