From: Daniel Vetter <daniel@ffwll.ch>
To: "Christian König" <christian.koenig@amd.com>
Cc: Dave Airlie <airlied@linux.ie>,
dri-devel <dri-devel@lists.freedesktop.org>,
Dave Airlie <airlied@gmail.com>,
amd-gfx list <amd-gfx@lists.freedesktop.org>,
Daniel Vetter <daniel@ffwll.ch>
Subject: Re: [PATCH] drm/radeon: fix check order in radeon_bo_move
Date: Fri, 27 Nov 2020 16:09:42 +0100 [thread overview]
Message-ID: <20201127150942.GF401619@phenom.ffwll.local> (raw)
In-Reply-To: <5a88c54c-3731-856a-da3c-b084c9b33187@amd.com>
On Fri, Nov 27, 2020 at 03:49:31PM +0100, Christian König wrote:
> Am 27.11.20 um 15:46 schrieb Daniel Vetter:
> > On Fri, Nov 27, 2020 at 3:10 PM Christian König
> > <ckoenig.leichtzumerken@gmail.com> wrote:
> > > Am 27.11.20 um 09:31 schrieb Dave Airlie:
> > > > Oops sorry for delay LGTM
> > > >
> > > > Reviewed-by: Dave Airlie <airlied@redhat.com>
> > > Thanks.
> > >
> > > > On Fri, 27 Nov 2020 at 02:34, Daniel Vetter <daniel@ffwll.ch> wrote:
> > > > > On Wed, Nov 25, 2020 at 3:34 PM Christian König
> > > > > <ckoenig.leichtzumerken@gmail.com> wrote:
> > > > > > Reorder the code to fix checking if blitting is available.
> > > > > Might be good to explain why blitting might not be available, e.g.
> > > > > suspend/resume and or chip death and stuff like that.
> > > > >
> > > > > > Signed-off-by: Christian König <christian.koenig@amd.com>
> > > > > Needs Fixes: 28a68f828266 ("drm/radeon/ttm: use multihop")
> > > Why does the subject of the patch needs to be in "()" ? I was already
> > > wondering why dim sometimes complains about my Fixes tag.
> > Hm I thought that's the official style. I kinda hacked around on it
> > until linux-next stopped complaining about our Fixes: tags. Maybe it's
> > not quite accurately reflecting the current bikeshed. Iirc checkpatch
> > even complains when you leave out the commit before the sha1, at least
> > in free-form text in the commit message.
>
> Well "git log -1 --oneline 28a68f828266" gives me:
>
> 28a68f828266 drm/radeon/ttm: use multihop
>
> Which is what I would naturally expect here, but no idea what the official
> format should be.
dim cite $sha1 is our attempt at modelling it. And yeah it's just
bikeshedded differently for no good reason. And I just noticed that dim
cite doesn't include the commit before the sha1.
-Daniel
>
> Christian.
>
> > -Daniel
> >
> > > > > Btw
> > > > >
> > > > > $ dim fixes [sha1]
> > > > >
> > > > > generates that for you plus nice cc list of offenders. With the Fixes
> > > > > line added:
> > > > >
> > > > > Reviewed-by: Daniel Vetter <daniel.vetter@ffwll.ch>
> > > Thanks,
> > > Christian.
> > >
>
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx
prev parent reply other threads:[~2020-11-27 15:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-25 14:34 [PATCH] drm/radeon: fix check order in radeon_bo_move Christian König
2020-11-26 15:49 ` Christian König
2020-11-26 16:34 ` Daniel Vetter
2020-11-27 8:31 ` Dave Airlie
2020-11-27 14:10 ` Christian König
2020-11-27 14:46 ` Daniel Vetter
2020-11-27 14:49 ` Christian König
2020-11-27 15:09 ` 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=20201127150942.GF401619@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=airlied@gmail.com \
--cc=airlied@linux.ie \
--cc=amd-gfx@lists.freedesktop.org \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.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