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>,
	Mario Kleiner <mario.kleiner.de@gmail.com>,
	kbuild test robot <fengguang.wu@intel.com>,
	Julia Lawall <julia.lawall@lip6.fr>,
	Nicholas Kazlauskas <nicholas.kazlauskas@amd.com>,
	Dave Airlie <airlied@redhat.com>
Subject: linux-next: Fixes tags need some work in the amdgpu tree
Date: Mon, 18 Mar 2019 15:59:14 +1100	[thread overview]
Message-ID: <20190318155914.74b67033@canb.auug.org.au> (raw)

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

Hi Alex,

In commit

  4dc982bbdaad ("drm/amd/powerplay: fix memdup.cocci warnings")

Fixes tag

  Fixes: 76760fe3c00d ("drm/amd/powerplay: add function to store overdrive information for smu11")

has these problem(s):

  - Target SHA1 does not exist

Did you mean:

  ec95996ed982 ("drm/amd/powerplay: add function to store overdrive information for smu11")

In commit

  7b19bba58f77 ("drm/amd/display: Use vrr friendly pageflip throttling in DC.")

Fixes tag

  Fixes: bb47de736661 ("drm/amdgpu: Set FreeSync state using drm VRR

has these problem(s):

  - Subject has leading but no trailing parentheses
  - Subject has leading but no trailing quotes

Please do not wrap Fixes tags onto more than one line.

-- 
Cheers,
Stephen Rothwell

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

             reply	other threads:[~2019-03-18  4:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-18  4:59 Stephen Rothwell [this message]
2020-09-17 22:27 linux-next: Fixes tags need some work in the amdgpu tree Stephen Rothwell
2021-03-23 21:44 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=20190318155914.74b67033@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=airlied@redhat.com \
    --cc=alexdeucher@gmail.com \
    --cc=fengguang.wu@intel.com \
    --cc=julia.lawall@lip6.fr \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mario.kleiner.de@gmail.com \
    --cc=nicholas.kazlauskas@amd.com \
    /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.