All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Alex Deucher <alexdeucher@gmail.com>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Mauro Rossi <issor.oruam@gmail.com>,
	Bhawanpreet Lakha <Bhawanpreet.Lakha@amd.com>
Subject: linux-next: Fixes tags need some work in the amdgpu tree
Date: Fri, 18 Sep 2020 08:27:04 +1000	[thread overview]
Message-ID: <20200918082704.466c822a@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 873 bytes --]

Hi all,

In commit

  2561adedd576 ("drm/amd/display: dc/clk_mgr: make function static")

Fixes tag

  Fixes: 3ecb3b794e2 "drm/amd/display: dc/clk_mgr: add support for SI parts (v2)"

has these problem(s):

  - SHA1 should be at least 12 digits long
    Can be fixed 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").

In commit

  d5c0af573279 ("drm/amd/display: Add missing "Copy GSL groups when committing a new context"")

Fixes tag

  Fixes: b6e881c9474 ("drm/amd/display: update navi to use new surface programming behaviour")

has these problem(s):

  - SHA1 should be at least 12 digits long
    Can be fixed 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").

-- 
Cheers,
Stephen Rothwell

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

             reply	other threads:[~2020-09-17 22:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-17 22:27 Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-03-23 21:44 linux-next: Fixes tags need some work in the amdgpu tree Stephen Rothwell
2019-03-18  4:59 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=20200918082704.466c822a@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=Bhawanpreet.Lakha@amd.com \
    --cc=alexdeucher@gmail.com \
    --cc=issor.oruam@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.