From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Alex Deucher <alexdeucher@gmail•com>
Cc: Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: linux-next: duplicate patches in the amdgpu tree
Date: Mon, 16 Jan 2023 08:17:10 +1100 [thread overview]
Message-ID: <20230116081710.7800a5c5@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 764 bytes --]
Hi all,
The following commits are also in Linus Torvalds' tree as different
commits (but the same patches):
08e60fac1d8c ("drm/amdgpu: Fix potential NULL dereference")
3693c1aea9b7 ("drm/amd/pm: add the missing mapping for PPT feature on SMU13.0.0 and 13.0.7")
40794dfd20e0 ("drm/amdgpu: Fixed bug on error when unloading amdgpu")
45bf79719f1f ("drm/amd/pm/smu13: BACO is supported when it's in BACO state")
7f347e3f8217 ("drm/amdkfd: Fix NULL pointer error for GC 11.0.1 on mGPU")
8ce1d255147a ("drm/amdkfd: Add sync after creating vram bo")
b7cdb41e7d25 ("drm/amd: Delay removal of the firmware framebuffer")
c595637f8a7c ("drm/amd/pm: correct the reference clock for fan speed(rpm) calculation")
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2023-01-15 21:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-15 21:17 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-01-22 21:04 linux-next: duplicate patches in the amdgpu tree Stephen Rothwell
2023-01-08 2:12 Stephen Rothwell
2023-01-05 23:58 Stephen Rothwell
2023-01-04 21:45 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=20230116081710.7800a5c5@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=alexdeucher@gmail$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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