linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Dave Airlie <airlied@linux.ie>, DRI <dri-devel@lists.freedesktop.org>
Cc: Alex Deucher <alexander.deucher@amd.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: Fixes tag needs some work in the drm-fixes tree
Date: Fri, 30 Oct 2020 15:42:35 +1100	[thread overview]
Message-ID: <20201030154235.22883451@canb.auug.org.au> (raw)

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

Hi all,

In commit

  65d437b83b2b ("drm/amdgpu/pm: fix the fan speed in fan1_input in manual mode for navi1x")

Fixes tag

  Fixes: 3033e9f1c2de ("drm/amdgpu/swsmu: handle manual fan readback on SMU11")

has these problem(s):

  - Target SHA1 does not exist

Mayne you meant

Fixes: f6eb433954bf ("drm/amdgpu/swsmu: handle manual fan readback on SMU11")

-- 
Cheers,
Stephen Rothwell

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

             reply	other threads:[~2020-10-30  4:42 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-30  4:42 Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-10-28  4:35 linux-next: Fixes tag needs some work in the drm-fixes tree Stephen Rothwell
2021-10-12 10:36 Stephen Rothwell
2020-07-27 13:38 Stephen Rothwell
2020-07-28  9:50 ` Daniel Vetter
2019-12-12 11:52 Stephen Rothwell
2019-12-12 12:35 ` Hans de Goede
2019-05-31  6:11 Stephen Rothwell
2019-04-17 21:46 Stephen Rothwell
2019-04-18  7:39 ` Daniel Vetter
2019-02-08 11:01 Stephen Rothwell
2019-02-08 11:31 ` Heiko Stübner
2019-02-08 11:40   ` Stephen Rothwell
2019-02-08 11:45     ` Heiko Stübner
2019-01-18  4:42 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=20201030154235.22883451@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=airlied@linux.ie \
    --cc=alexander.deucher@amd.com \
    --cc=dri-devel@lists.freedesktop.org \
    --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 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).