All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chen Li <chenli@uniontech.com>
To: Alex Deucher <alexdeucher@gmail.com>
Cc: "Alex Deucher" <alexander.deucher@amd.com>,
	"amd-gfx list" <amd-gfx@lists.freedesktop.org>,
	"Christian König" <christian.koenig@amd.com>,
	"Maling list - DRI developers" <dri-devel@lists.freedesktop.org>
Subject: [PATCH v2 0/2] use memcpy_to/fromio for UVD fw upload
Date: Fri, 04 Jun 2021 11:00:22 +0800	[thread overview]
Message-ID: <87mts6fi61.wl-chenli@uniontech.com> (raw)
In-Reply-To: <CADnq5_PorxhXnVXY8NxqjTj-1y-n0589QSiqUQc=QGNVhzP0xw@mail.gmail.com>


changelog:
    v1->v2: split sparse and memcp/memset fix

Chen Li (2):
  radeon: fix coding issues reported from sparse
  radeon: use memcpy_to/fromio for UVD fw upload

 drivers/gpu/drm/radeon/radeon_uvd.c | 30 ++++++++++++++++-------------
 1 file changed, 17 insertions(+), 13 deletions(-)

-- 
2.31.1



_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx

WARNING: multiple messages have this Message-ID (diff)
From: Chen Li <chenli@uniontech.com>
To: Alex Deucher <alexdeucher@gmail.com>
Cc: "Alex Deucher" <alexander.deucher@amd.com>,
	"amd-gfx list" <amd-gfx@lists.freedesktop.org>,
	"Christian König" <christian.koenig@amd.com>,
	"Maling list - DRI developers" <dri-devel@lists.freedesktop.org>
Subject: [PATCH v2 0/2] use memcpy_to/fromio for UVD fw upload
Date: Fri, 04 Jun 2021 11:00:22 +0800	[thread overview]
Message-ID: <87mts6fi61.wl-chenli@uniontech.com> (raw)
In-Reply-To: <CADnq5_PorxhXnVXY8NxqjTj-1y-n0589QSiqUQc=QGNVhzP0xw@mail.gmail.com>


changelog:
    v1->v2: split sparse and memcp/memset fix

Chen Li (2):
  radeon: fix coding issues reported from sparse
  radeon: use memcpy_to/fromio for UVD fw upload

 drivers/gpu/drm/radeon/radeon_uvd.c | 30 ++++++++++++++++-------------
 1 file changed, 17 insertions(+), 13 deletions(-)

-- 
2.31.1




  reply	other threads:[~2021-06-04  3:39 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-03  5:35 [PATCH] radeon: use memcpy_to/fromio for UVD fw upload Chen Li
2021-06-03  5:35 ` Chen Li
2021-06-03 19:21 ` Alex Deucher
2021-06-03 19:21   ` Alex Deucher
2021-06-04  3:00   ` Chen Li [this message]
2021-06-04  3:00     ` [PATCH v2 0/2] " Chen Li
2021-06-04  3:02 ` [PATCH v2 1/2] radeon: fix coding issues reported from sparse Chen Li
2021-06-04  3:02   ` Chen Li
2021-06-04  7:14   ` Christian König
2021-06-04  7:14     ` Christian König
2021-06-04  3:04 ` [PATCH v2 2/2] radeon: use memcpy_to/fromio for UVD fw upload Chen Li
2021-06-04  3:04   ` Chen Li
2021-06-04  7:18   ` Christian König
2021-06-04  7:18     ` Christian König
2021-06-04  7:50     ` [PATCH v3 0/2] " Chen Li
2021-06-04  7:50       ` Chen Li
2021-06-04  7:52     ` [PATCH v3 1/2] radeon: fix coding issues reported from sparse Chen Li
2021-06-04  7:52       ` Chen Li
2021-06-04  7:53     ` [PATCH v3 2/2] radeon: use memcpy_to/fromio for UVD fw upload Chen Li
2021-06-04  7:53       ` Chen Li
2021-06-04  8:08       ` Christian König
2021-06-04  8:08         ` Christian König
2021-06-04  8:28         ` Chen Li
2021-06-04  8:28           ` Chen Li
2021-06-04  8:31           ` Christian König
2021-06-04  8:31             ` Christian König
2021-06-04  8:37             ` Chen Li
2021-06-04  8:37               ` Chen Li
2021-06-04  8:38         ` [PATCH v4 0/2] " Chen Li
2021-06-04  8:38           ` Chen Li
2021-06-04  8:40         ` [PATCH v4 1/2] radeon: fix coding issues reported from sparse Chen Li
2021-06-04  8:40           ` Chen Li
2021-06-04 17:19           ` Alex Deucher
2021-06-04 17:19             ` Alex Deucher
2021-06-04  8:43         ` [PATCH v4 2/2] radeon: use memcpy_to/fromio for UVD fw upload Chen Li
2021-06-04  8:43           ` Chen Li
2021-06-04  8:47           ` Christian König
2021-06-04  8:47             ` Christian König
2021-06-04 17:21           ` Alex Deucher
2021-06-04 17:21             ` Alex Deucher

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=87mts6fi61.wl-chenli@uniontech.com \
    --to=chenli@uniontech.com \
    --cc=alexander.deucher@amd.com \
    --cc=alexdeucher@gmail.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=christian.koenig@amd.com \
    --cc=dri-devel@lists.freedesktop.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 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.