linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alex Deucher <alexdeucher@gmail.com>
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>
Subject: Re: linux-next: Fixes tag needs some work in the amdgpu tree
Date: Wed, 2 Mar 2022 18:43:41 -0500	[thread overview]
Message-ID: <CADnq5_PEobgWeJu8jipJx0gxSiiDiKLp372+5GLvTqncdG6zHA@mail.gmail.com> (raw)
In-Reply-To: <4804f1e7-8a25-ad8c-dd63-589ed34260c6@amd.com>

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

  reply	other threads:[~2022-03-02 23:45 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-02 20:57 linux-next: Fixes tag needs some work in the amdgpu tree Stephen Rothwell
2022-03-02 22:11 ` Luben Tuikov
2022-03-02 23:43   ` Alex Deucher [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-02-27 21:33 Stephen Rothwell
2025-02-25 21:31 Stephen Rothwell
2024-05-08 22:23 Stephen Rothwell
2024-05-10  8:56 ` Michel Dänzer
2024-05-10 15:40   ` Alex Deucher
2024-05-02 22:50 Stephen Rothwell
2023-03-14 21:37 Stephen Rothwell
2023-02-08 22:54 Stephen Rothwell
2022-06-30 22:56 Stephen Rothwell
2022-06-30 23:33 ` Alex Deucher
2022-06-11  9:55 Stephen Rothwell
2022-06-14 22:33 ` Stephen Rothwell
2022-03-06 20:26 Stephen Rothwell
2022-02-09 21:19 Stephen Rothwell
2022-01-25 22:40 Stephen Rothwell
2022-01-25 22:59 ` Luben Tuikov
2022-01-25 23:01   ` Alex Deucher
2022-01-23  5:41 Stephen Rothwell
2022-01-24 14:05 ` Luben Tuikov
2021-11-17 22:50 Stephen Rothwell
2021-11-09 22:01 Stephen Rothwell
2021-10-28  0:14 Stephen Rothwell
2021-09-14 21:17 Stephen Rothwell
2021-07-08 21:37 Stephen Rothwell
2021-07-09  7:42 ` Dan Carpenter
2021-07-09 13:01   ` Alex Deucher
2021-06-02 22:39 Stephen Rothwell
2021-06-03 10:15 ` Michel Dänzer
2021-05-11 22:19 Stephen Rothwell
2021-05-11 22:17 Stephen Rothwell
2021-05-10 22:42 Stephen Rothwell
2021-05-10 23:08 ` David Ward
2021-05-11 13:40   ` Alex Deucher
2021-03-08  2:07 Stephen Rothwell
2021-01-26  8:58 Stephen Rothwell
2020-10-27 21:22 Stephen Rothwell
2020-09-22 21:33 Stephen Rothwell
2020-06-23 22:45 Stephen Rothwell
2020-05-27 23:29 Stephen Rothwell
2019-12-18 21:25 Stephen Rothwell
2019-12-19  1:22 ` Chen, Guchun
2019-12-19  4:46   ` Alex Deucher
2019-12-20  0:52     ` Chen, Guchun
2019-11-26 19:44 Stephen Rothwell
2019-10-02 22:11 Stephen Rothwell
2019-10-04  6:26 ` S, Shirish
2019-03-18  4:54 Stephen Rothwell

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=CADnq5_PEobgWeJu8jipJx0gxSiiDiKLp372+5GLvTqncdG6zHA@mail.gmail.com \
    --to=alexdeucher@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=luben.tuikov@amd.com \
    --cc=sfr@canb.auug.org.au \
    /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).