linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Rob Clark <robdclark@gmail.com>, Sean Paul <seanpaul@chromium.org>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: linux-next: Fixes tag needs some work in the drm-msm tree
Date: Fri, 31 Jul 2020 08:28:04 +1000	[thread overview]
Message-ID: <20200731082804.34f0167b@canb.auug.org.au> (raw)

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

Hi all,

In commit

  4a8b6b60a159 ("drm/msm/adreno: fix gpu probe if no interconnect-names")

Fixes tag

  Fixes: 8e29fb37b301 ("drm/msm: handle for EPROBE_DEFER for of_icc_get")

has these problem(s):

  - Target SHA1 does not exist

Maybe you meant

Fixes: 08af4769c7d2 ("drm/msm: handle for EPROBE_DEFER for of_icc_get")

-- 
Cheers,
Stephen Rothwell

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

             reply	other threads:[~2020-07-30 22:28 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-30 22:28 Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-05-01 22:42 linux-next: Fixes tag needs some work in the drm-msm tree Stephen Rothwell
2022-05-01 22:39 Stephen Rothwell
2022-05-01 22:35 Stephen Rothwell
2022-03-02  0:43 Stephen Rothwell
2022-03-02  2:32 ` Dmitry Baryshkov
2021-10-04 21:25 Stephen Rothwell
2021-10-04 21:23 Stephen Rothwell
2021-06-17 22:32 Stephen Rothwell
2021-05-25  0:27 Stephen Rothwell
2021-05-08  2:16 Stephen Rothwell
2020-12-06 20:05 Stephen Rothwell
2020-12-06 21:05 ` Iskren Chernev
2020-12-06 21:57   ` Stephen Rothwell
2020-12-06 22:00     ` Stephen Rothwell
2020-11-04 20:41 Stephen Rothwell
2020-07-16  0:25 Stephen Rothwell
2020-07-14  0:02 Stephen Rothwell
2020-06-12  4:10 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=20200731082804.34f0167b@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=robdclark@gmail.com \
    --cc=seanpaul@chromium.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).