Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:18 as permitted sender) client-ip=2620:137:e000::1:18;
MIME-Version: 1.0
References: <20220303075733.481987a8@canb.auug.org.au> <4804f1e7-8a25-ad8c-dd63-589ed34260c6@amd.com>
In-Reply-To: <4804f1e7-8a25-ad8c-dd63-589ed34260c6@amd.com>
From:   Alex Deucher <alexdeucher@gmail.com>
Date:   Wed, 2 Mar 2022 18:43:41 -0500
Message-ID: <CADnq5_PEobgWeJu8jipJx0gxSiiDiKLp372+5GLvTqncdG6zHA@mail.gmail.com>
Subject: Re: linux-next: Fixes tag needs some work in the amdgpu tree
To:     Luben Tuikov <luben.tuikov@amd.com>
Cc:     Stephen Rothwell <sfr@canb.auug.org.au>,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
        Linux Next Mailing List <linux-next@vger.kernel.org>
Content-Type: text/plain; charset="UTF-8"
Precedence: bulk

On Wed, Mar 2, 2022 at 5:11 PM Luben Tuikov <luben.tuikov@amd.com> wrote:
>
> In our local branch it is:
>
>     60862e45da3b5a drm/amd/display: Don't fill up the logs
>     ...
>     Fixes: 5898243ba7acdb ("drm/amd/display: Add dsc pre-validation in atomic check")
>
> Which exists:
>
>     5898243ba7acdb drm/amd/display: Add dsc pre-validation in atomic check
>
> So maybe something happened in merging, etc.

That's the commit in our development branch, but that doesn't directly
correspond to the -next branch.  I've fixed it up and pushed a new
-next branch.

Alex

>
> Regards,
> Luben
>
> On 2022-03-02 15:57, Stephen Rothwell wrote:
> > Hi all,
> >
> > In commit
> >
> >   d15628d483a5 ("drm/amd/display: Don't fill up the logs")
> >
> > Fixes tag
> >
> >   Fixes: 5898243ba7acdb ("drm/amd/display: Add dsc pre-validation in atomic check")
> >
> > has these problem(s):
> >
> >   - Target SHA1 does not exist
> >
> > Maybe you meant
> >
> > Fixes: 17ce8a6907f7 ("drm/amd/display: Add dsc pre-validation in atomic check")
> >
>
> Regards,
> --
> Luben