From: Paulo Miguel Almeida <paulo.miguel.almeida.rodenas@gmail.com>
To: Felix Kuehling <felix.kuehling@amd.com>
Cc: "Pan, Xinhui" <Xinhui.Pan@amd.com>,
linux-kernel@vger.kernel.org, amd-gfx@lists.freedesktop.org,
dri-devel@lists.freedesktop.org,
"Daniel Vetter" <daniel@ffwll.ch>,
"Alex Deucher" <alexander.deucher@amd.com>,
"David Airlie" <airlied@gmail.com>,
"Christian König" <christian.koenig@amd.com>
Subject: Re: [PATCH] [next] amdkfd: remove unused kfd_pm4_headers_diq header file
Date: Wed, 26 Oct 2022 09:02:22 +1300 [thread overview]
Message-ID: <Y1hAzn9zXhQYj1NL@mail.google.com> (raw)
In-Reply-To: <f2b6f0e1-1ae0-21ec-372e-6e90827ccea6@amd.com>
On Tue, Oct 25, 2022 at 03:48:33PM -0400, Felix Kuehling wrote:
> Am 2022-10-25 um 05:12 schrieb Paulo Miguel Almeida:
> > kfd_pm4_headers_diq.h header is a leftover from the old H/W debugger
> > module support added on commit <fbeb661bfa895dc>. That implementation
> > was removed after a while and the last file that included that header
> > was removed on commit <5bdd3eb253544b1>.
> >
> > This patch removes the unused header file kfd_pm4_headers_diq.h
> >
> > Signed-off-by: Paulo Miguel Almeida <paulo.miguel.almeida.rodenas@gmail.com>
>
> Thank you for this patch and the one that removes struct cdit_header. I am
> applying both to our amd-staging-drm-next branch.
Thanks!
> <snip> I'm also fixing up the
> prefix of the commit headline to match our usual convention: drm/amdkfd: ...
Noted! (and much appreciated too). I will ensure I use the drm/amdkfd
prefix from now onwards.
Paulo A.
WARNING: multiple messages have this Message-ID (diff)
From: Paulo Miguel Almeida <paulo.miguel.almeida.rodenas@gmail.com>
To: Felix Kuehling <felix.kuehling@amd.com>
Cc: "Pan, Xinhui" <Xinhui.Pan@amd.com>,
linux-kernel@vger.kernel.org, amd-gfx@lists.freedesktop.org,
dri-devel@lists.freedesktop.org,
"Alex Deucher" <alexander.deucher@amd.com>,
"Christian König" <christian.koenig@amd.com>
Subject: Re: [PATCH] [next] amdkfd: remove unused kfd_pm4_headers_diq header file
Date: Wed, 26 Oct 2022 09:02:22 +1300 [thread overview]
Message-ID: <Y1hAzn9zXhQYj1NL@mail.google.com> (raw)
In-Reply-To: <f2b6f0e1-1ae0-21ec-372e-6e90827ccea6@amd.com>
On Tue, Oct 25, 2022 at 03:48:33PM -0400, Felix Kuehling wrote:
> Am 2022-10-25 um 05:12 schrieb Paulo Miguel Almeida:
> > kfd_pm4_headers_diq.h header is a leftover from the old H/W debugger
> > module support added on commit <fbeb661bfa895dc>. That implementation
> > was removed after a while and the last file that included that header
> > was removed on commit <5bdd3eb253544b1>.
> >
> > This patch removes the unused header file kfd_pm4_headers_diq.h
> >
> > Signed-off-by: Paulo Miguel Almeida <paulo.miguel.almeida.rodenas@gmail.com>
>
> Thank you for this patch and the one that removes struct cdit_header. I am
> applying both to our amd-staging-drm-next branch.
Thanks!
> <snip> I'm also fixing up the
> prefix of the commit headline to match our usual convention: drm/amdkfd: ...
Noted! (and much appreciated too). I will ensure I use the drm/amdkfd
prefix from now onwards.
Paulo A.
WARNING: multiple messages have this Message-ID (diff)
From: Paulo Miguel Almeida <paulo.miguel.almeida.rodenas@gmail.com>
To: Felix Kuehling <felix.kuehling@amd.com>
Cc: "Alex Deucher" <alexander.deucher@amd.com>,
"Christian König" <christian.koenig@amd.com>,
"Pan, Xinhui" <Xinhui.Pan@amd.com>,
"David Airlie" <airlied@gmail.com>,
"Daniel Vetter" <daniel@ffwll.ch>,
amd-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] [next] amdkfd: remove unused kfd_pm4_headers_diq header file
Date: Wed, 26 Oct 2022 09:02:22 +1300 [thread overview]
Message-ID: <Y1hAzn9zXhQYj1NL@mail.google.com> (raw)
In-Reply-To: <f2b6f0e1-1ae0-21ec-372e-6e90827ccea6@amd.com>
On Tue, Oct 25, 2022 at 03:48:33PM -0400, Felix Kuehling wrote:
> Am 2022-10-25 um 05:12 schrieb Paulo Miguel Almeida:
> > kfd_pm4_headers_diq.h header is a leftover from the old H/W debugger
> > module support added on commit <fbeb661bfa895dc>. That implementation
> > was removed after a while and the last file that included that header
> > was removed on commit <5bdd3eb253544b1>.
> >
> > This patch removes the unused header file kfd_pm4_headers_diq.h
> >
> > Signed-off-by: Paulo Miguel Almeida <paulo.miguel.almeida.rodenas@gmail.com>
>
> Thank you for this patch and the one that removes struct cdit_header. I am
> applying both to our amd-staging-drm-next branch.
Thanks!
> <snip> I'm also fixing up the
> prefix of the commit headline to match our usual convention: drm/amdkfd: ...
Noted! (and much appreciated too). I will ensure I use the drm/amdkfd
prefix from now onwards.
Paulo A.
next prev parent reply other threads:[~2022-10-25 20:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-25 9:12 [PATCH] [next] amdkfd: remove unused kfd_pm4_headers_diq header file Paulo Miguel Almeida
2022-10-25 9:12 ` Paulo Miguel Almeida
2022-10-25 19:48 ` Felix Kuehling
2022-10-25 20:02 ` Paulo Miguel Almeida [this message]
2022-10-25 20:02 ` Paulo Miguel Almeida
2022-10-25 20:02 ` Paulo Miguel Almeida
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=Y1hAzn9zXhQYj1NL@mail.google.com \
--to=paulo.miguel.almeida.rodenas@gmail.com \
--cc=Xinhui.Pan@amd.com \
--cc=airlied@gmail.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=christian.koenig@amd.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=felix.kuehling@amd.com \
--cc=linux-kernel@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 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.