dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Joe Perches <joe@perches.com>
Cc: "David Airlie" <airlied@linux.ie>,
	"Daniel Vetter" <daniel.vetter@ffwll.ch>,
	kernel-janitors@vger.kernel.org,
	LKML <linux-kernel@vger.kernel.org>,
	"amd-gfx list" <amd-gfx@lists.freedesktop.org>,
	"Alex Deucher" <alexander.deucher@amd.com>,
	"Maling list - DRI developers" <dri-devel@lists.freedesktop.org>,
	"Colin King" <colin.king@canonical.com>,
	"Christian König" <christian.koenig@amd.com>
Subject: Re: [PATCH] drm/amdgpu: fix spelling mistake "Falied" -> "Failed"
Date: Thu, 6 Aug 2020 09:36:41 +1000	[thread overview]
Message-ID: <20200806093641.5795690c@canb.auug.org.au> (raw)
In-Reply-To: <d720b466a2b4b7507a963f9a2605c7f81e82e7ba.camel@perches.com>


[-- Attachment #1.1: Type: text/plain, Size: 3706 bytes --]

Hi all,

On Wed, 05 Aug 2020 15:19:38 -0700 Joe Perches <joe@perches.com> wrote:
>
> On Wed, 2020-08-05 at 17:27 -0400, Alex Deucher wrote:
> > On Wed, Aug 5, 2020 at 4:53 PM Joe Perches <joe@perches.com> wrote:  
> > > On Wed, 2020-08-05 at 16:01 -0400, Alex Deucher wrote:  
> > > > On Wed, Aug 5, 2020 at 7:35 AM Colin King <colin.king@canonical.com> wrote:  
> > > > > From: Colin Ian King <colin.king@canonical.com>
> > > > > 
> > > > > There is a spelling mistake in a DRM_ERROR message. Fix it.
> > > > > 
> > > > > Signed-off-by: Colin Ian King <colin.king@canonical.com>  
> > > > 
> > > > This is already fixed.  
> > > 
> > > This fix is not in today's -next.
> > > 
> > > Perhaps whatever tree it's fixed in should be in -next.
> > >   
> > 
> > Weird.  It's in the drm-next tree as:
> > 
> > commit 4afaa61db9cf5250b5734c2531b226e7b3a3d691
> > Author: Colin Ian King <colin.king@canonical.com>
> > Date:   Fri Jul 10 09:37:58 2020 +0100
> > 
> >     drm/amdgpu: fix spelling mistake "Falied" -> "Failed"
> > 
> >     There is a spelling mistake in a DRM_ERROR error message. Fix it.
> > 
> >     Signed-off-by: Colin Ian King <colin.king@canonical.com>
> >     Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
> > 
> > Alex
> >   
> > > $ git show --oneline -s
> > > d15fe4ec0435 (HEAD, tag: next-20200805, origin/master, origin/HEAD) Add linux-next specific files for 20200805
> > > 
> > > $ git grep -i falied drivers
> > > drivers/gpu/drm/amd/amdgpu/amdgpu_psp.c:                DRM_ERROR("Falied to terminate tmr\n");
> > >   
> > > > > diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_psp.c b/drivers/gpu/drm/amd/amdgpu/amdgpu_psp.c  
> > > []  
> > > > > @@ -2010,7 +2010,7 @@ static int psp_suspend(void *handle)
> > > > > 
> > > > >         ret = psp_tmr_terminate(psp);
> > > > >         if (ret) {
> > > > > -               DRM_ERROR("Falied to terminate tmr\n");
> > > > > +               DRM_ERROR("Failed to terminate tmr\n");
> > > > >                 return ret;
> > > > >         }  
> 
> Dunno.
> 
> Maybe it's due to some ordering of trees in
> how -next accumulates patches?

The spelling error is introduced in two commits:

  c564b8601ae9 ("drm/amdgpu: add TMR destory function for psp")

in Linus' tree between v5.8-rc4 and rc5

  90937420c44f ("drm/amdgpu: add TMR destory function for psp")

in the amdgpu tree between two merges by the drm tree.  In this same
interval, the error is corrected by commit

  4afaa61db9cf ("drm/amdgpu: fix spelling mistake "Falied" -> "Failed"")

so when David comes to merge the amdgpu tree in commit

  206739119508 ("Merge tag 'amd-drm-next-5.9-2020-07-17' of git://people.freedesktop.org/~agd5f/linux into drm-next")

the spelling error has been introduced on one side of the merge and
introduced and corrected on the other.  This would have produced a
conflict which David presumably resolved in haste by picking the HEAD
side of the merge instead of the MERGE_HEAD side (it happens).

This could have been avoided by not cherry-picking fix commits around
in the amdgpu process - instead having a fixes branch that is merged
into the next branch after the fixes branch has been accepted upstream
(that way there is only one commit for each fix and less conflicts).

I have to deal with these sort of conflicts (sometimes daily) due to
the drm processes.  Its a pain as I have to track down each conflict to
see if the same patches appear on both sides of merges and then try to
figure out what other changes occur.  (This is only slightly helped by
have the "cherry-picked from" tags in the fix commits.)
-- 
Cheers,
Stephen Rothwell

[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

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

  reply	other threads:[~2020-08-05 23:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-05 11:35 [PATCH] drm/amdgpu: fix spelling mistake "Falied" -> "Failed" Colin King
2020-08-05 20:01 ` Alex Deucher
2020-08-05 20:53   ` Joe Perches
2020-08-05 21:27     ` Alex Deucher
2020-08-05 21:29       ` Colin Ian King
2020-08-05 22:19       ` Joe Perches
2020-08-05 23:36         ` Stephen Rothwell [this message]
2020-08-06  7:34           ` daniel

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=20200806093641.5795690c@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=airlied@linux.ie \
    --cc=alexander.deucher@amd.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=christian.koenig@amd.com \
    --cc=colin.king@canonical.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=joe@perches.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).