From: Bagas Sanjaya <bagasdotme@gmail.com>
To: "Tales Lelo da Aparecida" <tales.aparecida@gmail.com>,
"Alex Deucher" <alexander.deucher@amd.com>,
"Christian König" <christian.koenig@amd.com>,
"Pan, Xinhui" <Xinhui.Pan@amd.com>,
"David Airlie" <airlied@linux.ie>,
"Daniel Vetter" <daniel@ffwll.ch>,
"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
"Maxime Ripard" <mripard@kernel.org>,
"Thomas Zimmermann" <tzimmermann@suse.de>,
"Jonathan Corbet" <corbet@lwn.net>,
amd-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
andrealmeid@riseup.net
Subject: Re: [PATCH 2/2] MAINTAINERS: add docs entry to AMDGPU
Date: Sat, 16 Apr 2022 12:47:52 +0700 [thread overview]
Message-ID: <4f4c8441-a144-6c2d-0f8b-b598905c2f3d@gmail.com> (raw)
In-Reply-To: <20220415195027.305019-3-tales.aparecida@gmail.com>
On 4/16/22 02:50, Tales Lelo da Aparecida wrote:
> To make sure maintainers of amdgpu drivers are aware of any changes
> in their documentation, add its entry to MAINTAINERS.
>
Did you mean the Documentation/gpu/amdgpu/ is maintained by dri-devel?
--
An old man doll... just what I always wanted! - Clara
next prev parent reply other threads:[~2022-04-16 5:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-15 19:50 [PATCH 0/2] Update AMDGPU glossary and MAINTAINERS Tales Lelo da Aparecida
2022-04-15 19:50 ` [PATCH 1/2] Documentation/gpu: Add entries to amdgpu glossary Tales Lelo da Aparecida
2022-04-17 6:18 ` Paul Menzel
2022-04-19 14:59 ` Alex Deucher
2022-04-15 19:50 ` [PATCH 2/2] MAINTAINERS: add docs entry to AMDGPU Tales Lelo da Aparecida
2022-04-16 5:47 ` Bagas Sanjaya [this message]
2022-04-16 16:58 ` Tales
2022-04-16 13:00 ` [PATCH 0/2] Update AMDGPU glossary and MAINTAINERS Christian König
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=4f4c8441-a144-6c2d-0f8b-b598905c2f3d@gmail.com \
--to=bagasdotme@gmail.com \
--cc=Xinhui.Pan@amd.com \
--cc=airlied@linux.ie \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=andrealmeid@riseup.net \
--cc=christian.koenig@amd.com \
--cc=corbet@lwn.net \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=tales.aparecida@gmail.com \
--cc=tzimmermann@suse.de \
/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
Powered by JetHome