From: Saheed Bolarinwa <refactormyself@gmail.com>
To: Mauro Carvalho Chehab <mchehab@kernel.org>
Cc: Jonathan Corbet <corbet@lwn.net>,
linux-kernel-mentees@lists.linuxfoundation.org
Subject: Re: [Linux-kernel-mentees] Is anyone working on fixing warnings these Documentation files ?
Date: Tue, 21 Apr 2020 11:04:01 +0200 [thread overview]
Message-ID: <bd14efb7-6144-1e0d-7cff-459f6d1c9a94@gmail.com> (raw)
In-Reply-To: <20200420083617.7cdcbd1c@coco.lan>
On 4/20/20 8:36 AM, Mauro Carvalho Chehab wrote:
> Em Mon, 20 Apr 2020 02:56:18 +0200
> Saheed Bolarinwa <refactormyself@gmail.com> escreveu:
>
>> Hello,
>>
>> Please is there anyone working on fixing these files. I have have
>> checked the email archive,
>>
>> though I surely have not search thoroughly.
>>
>> Please, let me know if you are working on any of these:
>>
>>
>> - Documentation/admin-guide/ras.rst
>>
>> - Documentation/virt/kvm/amd-memory-encryption.rst
>>
>> - Documentation/trace/events.rst
>>
>> - Documentation/power/pm_qos_interface.rst
>>
>> - Documentation/process/programming-language.rst
>>
>> - Documentation/filesystems/fuse.rst
>>
>> - Documentation/admin-guide/bootconfig.rst
>>
>> - Documentation/admin-guide/hw-vuln/tsx_async_abort.rst
>>
>> - Documentation/filesystems/ubifs-authentication.rst
>>
>> - Documentation/driver-api/driver-model/driver.rst
>>
>> - Documentation/driver-api/gpio/driver.rst
>>
>> - Documentation/driver-api/thermal/cpu-idle-cooling.rst
> There is a set of fixes from me at:
>
> https://git.linuxtv.org/mchehab/experimental.git/log/?h=docs-fixes
>
> that were already submitted, but I guess Jon didn't merge yet.
>
> Btw, if you want to do any work, I suggest you to take a look on
> this tree:
>
> https://git.linuxtv.org/mchehab/experimental.git/log/?h=all-docs
>
> Where I merged all patches I did already for documentation and
> that weren't merged upstream yet.
Hello,
Thank you for the response, I have checked the link you gave:
https://git.linuxtv.org/mchehab/experimental.git/log/?h=all-docs
I am not sure if it is the best way to figure out what is not being
worked on,
but what I did was to search for the files I listed previously and I
could not
find the ones listed below:
- Documentation/admin-guide/ras.rst
- Documentation/virt/kvm/amd-memory-encryption.rst
- Documentation/admin-guide/hw-vuln/tsx_async_abort.rst
- Documentation/filesystems/ubifs-authentication.rst
- Documentation/driver-api/driver-model/driver.rst
Can I assume they are not being worked on, at least by you?
Thank you.
- Saheed
_______________________________________________
Linux-kernel-mentees mailing list
Linux-kernel-mentees@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/linux-kernel-mentees
next prev parent reply other threads:[~2020-04-21 10:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-20 0:56 [Linux-kernel-mentees] Is anyone working on fixing warnings these Documentation files ? Saheed Bolarinwa
2020-04-20 6:36 ` Mauro Carvalho Chehab
2020-04-21 9:04 ` Saheed Bolarinwa [this message]
2020-04-21 10:45 ` Mauro Carvalho Chehab
2020-04-22 17:53 ` Saheed Bolarinwa
2020-04-22 19:09 ` Mauro Carvalho Chehab
2020-04-22 19:45 ` Saheed Bolarinwa
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=bd14efb7-6144-1e0d-7cff-459f6d1c9a94@gmail.com \
--to=refactormyself@gmail.com \
--cc=corbet@lwn.net \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=mchehab@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;
as well as URLs for NNTP newsgroup(s).