From: Carlos Bilbao <carlos.bilbao@amd.com>
To: Jonathan Corbet <corbet@lwn.net>, lukas.bulwahn@gmail.com
Cc: linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
bilbao@vt.edu, ojeda@kernel.org, lstoakes@gmail.com
Subject: Re: [PATCH 0/2] kernel-docs: New maintainer and Spanish translation
Date: Thu, 24 Nov 2022 09:40:15 -0600 [thread overview]
Message-ID: <af881ad1-1b40-a22e-08ca-44d75a48b90c@amd.com> (raw)
In-Reply-To: <87a64h8wu6.fsf@meer.lwn.net>
On 11/23/22 10:22, Jonathan Corbet wrote:
> Carlos Bilbao <carlos.bilbao@amd.com> writes:
>
>> I don't know if that would have any success. Worst-case scenario, we end up
>> with an equally outdated list of resources in a few years. But maybe it's
>> worth a try?
> I'm certainly not opposed to trying! :)
I'm starting a new patch set with this, and translating coding-style.rst,
after fixing the organization of sp_SP/.
>
> Thanks,
>
> jon
Thanks,
Carlos
prev parent reply other threads:[~2022-11-24 15:40 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
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 [this message]
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=af881ad1-1b40-a22e-08ca-44d75a48b90c@amd.com \
--to=carlos.bilbao@amd.com \
--cc=bilbao@vt.edu \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lstoakes@gmail.com \
--cc=lukas.bulwahn@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