linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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: Signed-off-by missing for commit in the amdgpu tree
Date: Mon, 22 Mar 2021 08:17:28 +1100	[thread overview]
Message-ID: <20210322081728.68875899@canb.auug.org.au> (raw)

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

Hi all,

Commits

  42b44dbf555c ("drm/amdgpu: Enable VCN/JPEG CG on aldebaran")
  19eb0ec1d1a2 ("drm/amdgpu: add codes to capture invalid hardware access when recovery")

are missing a Signed-off-by from their committer.

-- 
Cheers,
Stephen Rothwell

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

             reply	other threads:[~2021-03-21 21:18 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-21 21:17 Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-07-09 22:25 linux-next: Signed-off-by missing for commit in the amdgpu tree Stephen Rothwell
2023-07-10 13:21 ` Aurabindo Pillai
2023-07-10 13:24   ` Alex Deucher
2023-01-09 21:58 Stephen Rothwell
2023-01-09 22:04 ` Alex Deucher
2022-07-13 22:22 Stephen Rothwell
2022-06-01 21:57 Stephen Rothwell
2022-05-14 10:11 Stephen Rothwell
2022-01-11 21:23 Stephen Rothwell
2022-01-03 23:50 Stephen Rothwell
2021-03-28 21:24 Stephen Rothwell
2021-03-29 14:17 ` Mark Yacoub
2021-03-29 15:34   ` Alex Deucher
2021-03-29 15:35     ` Mark Yacoub
2020-11-01 21:28 Stephen Rothwell
2020-09-15 22:27 Stephen Rothwell
2020-01-27 21:38 Stephen Rothwell
2019-07-16 19:37 Stephen Rothwell
2019-07-03 21:43 Stephen Rothwell
2019-06-22 13:54 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=20210322081728.68875899@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=alexdeucher@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 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).