From: Grzegorz Zdanowski <grzegorz129@gmail.com>
To: linux-doc@vger.kernel.org
Subject: Are documentation-only patches welcomed?
Date: Sat, 12 Jun 2021 12:26:06 -0500 [thread overview]
Message-ID: <CAAoDVDDCWKw9_uh6i70zW6uCH_bvuBWyQV7u=TW_ne9CaWA0rQ@mail.gmail.com> (raw)
Hi!
While dipping my toes in Linux kernel programming I discovered that a
lot of functions, even exported ones, lack any comment blocks or
references to documentation. Most of the time I have to resort to the
original commit message + LKML threads associated with a given
function.
Is this intentional, or is it simply a by-product of the lack of
developer's time? If it's the latter, are documentation-only patches
welcomed?
Regards,
Greg.
next reply other threads:[~2021-06-12 17:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-12 17:26 Grzegorz Zdanowski [this message]
2021-06-12 19:33 ` Are documentation-only patches welcomed? Matthew Wilcox
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='CAAoDVDDCWKw9_uh6i70zW6uCH_bvuBWyQV7u=TW_ne9CaWA0rQ@mail.gmail.com' \
--to=grzegorz129@gmail.com \
--cc=linux-doc@vger.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 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.