From: Tales <tales.aparecida@gmail.com>
To: Bagas Sanjaya <bagasdotme@gmail.com>
Cc: "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,
"André Almeida" <andrealmeid@riseup.net>
Subject: Re: [PATCH 2/2] MAINTAINERS: add docs entry to AMDGPU
Date: Sat, 16 Apr 2022 13:58:12 -0300 [thread overview]
Message-ID: <CAGVoLp75WEWxk2uTz6AtomRo+5kNexqM-+aLHQe8pSp66PcHzQ@mail.gmail.com> (raw)
In-Reply-To: <4f4c8441-a144-6c2d-0f8b-b598905c2f3d@gmail.com>
Hi Bagas Sanjaya,
Em sáb., 16 de abr. de 2022 às 02:47, Bagas Sanjaya
<bagasdotme@gmail.com> escreveu:
> 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?
`Documentation/gpu/amdgpu/` should be maintained by "RADEON and AMDGPU
DRM DRIVERS" developers, which are part of the dri-devel community.
Kind regards
WARNING: multiple messages have this Message-ID (diff)
From: Tales <tales.aparecida@gmail.com>
To: Bagas Sanjaya <bagasdotme@gmail.com>
Cc: "Thomas Zimmermann" <tzimmermann@suse.de>,
"Jonathan Corbet" <corbet@lwn.net>,
"David Airlie" <airlied@linux.ie>,
dri-devel@lists.freedesktop.org, "Pan,
Xinhui" <Xinhui.Pan@amd.com>,
"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
linux-kernel@vger.kernel.org,
"Maxime Ripard" <mripard@kernel.org>,
linux-doc@vger.kernel.org, amd-gfx@lists.freedesktop.org,
"Daniel Vetter" <daniel@ffwll.ch>,
"Alex Deucher" <alexander.deucher@amd.com>,
"André Almeida" <andrealmeid@riseup.net>,
"Christian König" <christian.koenig@amd.com>
Subject: Re: [PATCH 2/2] MAINTAINERS: add docs entry to AMDGPU
Date: Sat, 16 Apr 2022 13:58:12 -0300 [thread overview]
Message-ID: <CAGVoLp75WEWxk2uTz6AtomRo+5kNexqM-+aLHQe8pSp66PcHzQ@mail.gmail.com> (raw)
In-Reply-To: <4f4c8441-a144-6c2d-0f8b-b598905c2f3d@gmail.com>
Hi Bagas Sanjaya,
Em sáb., 16 de abr. de 2022 às 02:47, Bagas Sanjaya
<bagasdotme@gmail.com> escreveu:
> 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?
`Documentation/gpu/amdgpu/` should be maintained by "RADEON and AMDGPU
DRM DRIVERS" developers, which are part of the dri-devel community.
Kind regards
WARNING: multiple messages have this Message-ID (diff)
From: Tales <tales.aparecida@gmail.com>
To: Bagas Sanjaya <bagasdotme@gmail.com>
Cc: "Thomas Zimmermann" <tzimmermann@suse.de>,
"Jonathan Corbet" <corbet@lwn.net>,
"David Airlie" <airlied@linux.ie>,
dri-devel@lists.freedesktop.org, "Pan,
Xinhui" <Xinhui.Pan@amd.com>,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
amd-gfx@lists.freedesktop.org,
"Alex Deucher" <alexander.deucher@amd.com>,
"André Almeida" <andrealmeid@riseup.net>,
"Christian König" <christian.koenig@amd.com>
Subject: Re: [PATCH 2/2] MAINTAINERS: add docs entry to AMDGPU
Date: Sat, 16 Apr 2022 13:58:12 -0300 [thread overview]
Message-ID: <CAGVoLp75WEWxk2uTz6AtomRo+5kNexqM-+aLHQe8pSp66PcHzQ@mail.gmail.com> (raw)
In-Reply-To: <4f4c8441-a144-6c2d-0f8b-b598905c2f3d@gmail.com>
Hi Bagas Sanjaya,
Em sáb., 16 de abr. de 2022 às 02:47, Bagas Sanjaya
<bagasdotme@gmail.com> escreveu:
> 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?
`Documentation/gpu/amdgpu/` should be maintained by "RADEON and AMDGPU
DRM DRIVERS" developers, which are part of the dri-devel community.
Kind regards
next prev parent reply other threads:[~2022-04-16 16:58 UTC|newest]
Thread overview: 14+ 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-17 6:18 ` Paul Menzel
2022-04-17 6:18 ` Paul Menzel
2022-04-19 14:59 ` Alex Deucher
2022-04-19 14:59 ` Alex Deucher
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
2022-04-16 16:58 ` Tales [this message]
2022-04-16 16:58 ` Tales
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=CAGVoLp75WEWxk2uTz6AtomRo+5kNexqM-+aLHQe8pSp66PcHzQ@mail.gmail.com \
--to=tales.aparecida@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=bagasdotme@gmail.com \
--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=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 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.