The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Carlos Bilbao <carlos.bilbao@amd.com>
To: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
Cc: corbet@lwn.net, lukas.bulwahn@gmail.com, Dhaval.Giani@amd.com,
	linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
	bilbao@vt.edu, ojeda@kernel.org
Subject: Re: [PATCH 1/2] docs: Update maintainer of kernel-docs.rst
Date: Fri, 18 Nov 2022 12:27:37 -0600	[thread overview]
Message-ID: <1ee66e1e-4ea0-1a6e-92fd-60831dd938b4@amd.com> (raw)
In-Reply-To: <CANiq72nN7i4yXjnLftdKZ7zo8Qw8c=aM6L+D2SvzH47PVALJYQ@mail.gmail.com>

On 11/18/22 11:52, Miguel Ojeda wrote:

> On Fri, Nov 18, 2022 at 6:09 PM Carlos Bilbao <carlos.bilbao@amd.com> wrote:
>>   Index of Further Kernel Documentation
>>   =====================================
>>
>> +Current Maintainer: Carlos Bilbao <carlos.bilbao@amd.com>
>> +
>>   Initial Author: Juan-Mariano de Goyeneche (<jmseyas@dit.upm.es>;
>>   email address is defunct now.)
> Shouldn't this be covered via `MAINTAINERS`?


Ah, you are right, something like in:

CODE OF CONDUCT
M:      Greg Kroah-Hartman <gregkh@linuxfoundation.org>
S:      Supported
F:      Documentation/process/code-of-conduct-interpretation.rst
F:      Documentation/process/code-of-conduct.rst


>
> Cheers,
> Miguel


Thanks,
Carlos


  reply	other threads:[~2022-11-18 18:29 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-18 17:09 [PATCH 0/2] kernel-docs: New maintainer and Spanish translation Carlos Bilbao
2022-11-18 17:09 ` [PATCH 1/2] docs: Update maintainer of kernel-docs.rst Carlos Bilbao
2022-11-18 17:52   ` Miguel Ojeda
2022-11-18 18:27     ` Carlos Bilbao [this message]
2022-11-18 18:53       ` Miguel Ojeda
2022-11-18 17:09 ` [PATCH 2/2] docs/sp_SP: Add process kernel-docs translation Carlos Bilbao
2022-11-18 17:12 ` [PATCH 0/2] kernel-docs: New maintainer and Spanish translation Carlos Bilbao
2022-11-18 17:56 ` Miguel Ojeda
2022-11-18 18:30   ` Carlos Bilbao
2022-11-21 20:58 ` Jonathan Corbet
2022-11-23 16:19   ` Carlos Bilbao
2022-11-23 16:22     ` Jonathan Corbet
2022-11-24 15:40       ` Carlos Bilbao

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=1ee66e1e-4ea0-1a6e-92fd-60831dd938b4@amd.com \
    --to=carlos.bilbao@amd.com \
    --cc=Dhaval.Giani@amd.com \
    --cc=bilbao@vt.edu \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lukas.bulwahn@gmail.com \
    --cc=miguel.ojeda.sandonis@gmail.com \
    --cc=ojeda@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