From: Alex Deucher <alexdeucher@gmail.com>
To: "Michel Dänzer" <mdaenzer@redhat.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: Fri, 10 May 2024 11:40:51 -0400 [thread overview]
Message-ID: <CADnq5_Nk0qZzBPJaBYVBjuEOxaTDtXu2tosGyZigum5rnz2fRw@mail.gmail.com> (raw)
In-Reply-To: <2b3ea2b9-1959-40ff-b8f9-5ad1569f72be@redhat.com>
On Fri, May 10, 2024 at 4:56 AM Michel Dänzer <mdaenzer@redhat.com> wrote:
>
> On 2024-05-09 00:23, Stephen Rothwell wrote:
> > Hi all,
> >
> > In commit
> >
> > 27557a840463 ("drm/amdgpu: Fix comparison in amdgpu_res_cpu_visible")
> >
> > Fixes tag
> >
> > Fixes: a6ff969fe9 ("drm/amdgpu: fix visible VRAM handling during faults")
> >
> > has these problem(s):
> >
> > - SHA1 should be at least 12 digits long
> > This can be fixed for the future by setting core.abbrev to 12 (or
> > more) or (for git v2.11 or later) just making sure it is not set
> > (or set to "auto").
>
> It wouldn't have helped, since I pruned it manually from the full hash
> (from gitk). The intention was pruning to 12 as always, apparently I
> miscounted though. Oops.
I've fixed it up and repushed.
Alex
>
>
> --
> Earthling Michel Dänzer | https://redhat.com
> Libre software enthusiast | Mesa and Xwayland developer
>
next prev parent reply other threads:[~2024-05-10 15:41 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-08 22:23 linux-next: Fixes tag needs some work in the amdgpu tree Stephen Rothwell
2024-05-10 8:56 ` Michel Dänzer
2024-05-10 15:40 ` Alex Deucher [this message]
-- strict thread matches above, loose matches on Subject: below --
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-03-02 20:57 Stephen Rothwell
2022-03-02 22:11 ` Luben Tuikov
2022-03-02 23:43 ` Alex Deucher
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_Nk0qZzBPJaBYVBjuEOxaTDtXu2tosGyZigum5rnz2fRw@mail.gmail.com \
--to=alexdeucher@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mdaenzer@redhat.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 read-only IMAP folder(s) and NNTP newsgroup(s).