From: Alex Deucher <alexdeucher@gmail.com>
To: David Ward <david.ward@gatech.edu>
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: Tue, 11 May 2021 09:40:46 -0400 [thread overview]
Message-ID: <CADnq5_NNaOEe22WoyKmrXbe5rZMx-t7KoOZay-uSYa6s2eAv8A@mail.gmail.com> (raw)
In-Reply-To: <f2fd1c01-d559-b8ac-b342-897c74ae852b@gatech.edu>
I'll fix it up.
Alex
On Mon, May 10, 2021 at 7:08 PM David Ward <david.ward@gatech.edu> wrote:
>
> On 5/10/21 6:42 PM, Stephen Rothwell wrote:
> > Hi all,
> >
> > In commit
> >
> > 0b62b6ed6959 ("drm/amd/display: Initialize attribute for hdcp_srm sysfs file")
> >
> > Fixes tag
> >
> > Fixes: a193ed2094ba ("drm/amd/display: Add sysfs interface for set/get srm")
> >
> > has these problem(s):
> >
> > - Subject does not match target commit subject
> > Just use
> > git log -1 --format='Fixes: %h ("%s")'
> >
> > Maybe you meant
> >
> > Fixes: 9037246bb2da ("drm/amd/display: Add sysfs interface for set/get srm")
> >
> My apologies. The correct hash is in fact 9037246bb2da. (Commit
> a193ed2094ba introduced HDCP handling in amdgpu_pm, but did not include
> the sysfs file.) It seems I inadvertently copied the wrong hash when
> preparing the commit message.
>
> Please let me know if I need to resubmit this patch.
>
> Thank you,
>
> David
>
>
next prev parent reply other threads:[~2021-05-11 13:41 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-10 22:42 linux-next: Fixes tag needs some work in the amdgpu tree Stephen Rothwell
2021-05-10 23:08 ` David Ward
2021-05-11 13:40 ` Alex Deucher [this message]
-- strict thread matches above, loose matches on Subject: below --
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-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_NNaOEe22WoyKmrXbe5rZMx-t7KoOZay-uSYa6s2eAv8A@mail.gmail.com \
--to=alexdeucher@gmail.com \
--cc=david.ward@gatech.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--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).