From: Jonathan Corbet <corbet@lwn.net>
To: Qi Zheng <arch0.zheng@gmail.com>
Cc: gregkh@linuxfoundation.org, rafael@kernel.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kobject: documentation: Fix erroneous function example in kobject doc.
Date: Tue, 5 May 2020 09:38:04 -0600 [thread overview]
Message-ID: <20200505093804.6d39abef@lwn.net> (raw)
In-Reply-To: <20200505061828.42952-1-arch0.zheng@gmail.com>
On Tue, 5 May 2020 14:18:28 +0800
Qi Zheng <arch0.zheng@gmail.com> wrote:
> Update the definitions of some functions listed in the kobject
> document, since they have been changed.
>
> Signed-off-by: Qi Zheng <arch0.zheng@gmail.com>
I've applied this since it's an improvement on the original. The proper
fix, though, is to bring in the nice kerneldoc comments that those
functions have rather than trying to maintain another copy of that
information.
Thanks,
jon
prev parent reply other threads:[~2020-05-05 15:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-05 6:18 [PATCH] kobject: documentation: Fix erroneous function example in kobject doc Qi Zheng
2020-05-05 15:38 ` Jonathan Corbet [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=20200505093804.6d39abef@lwn.net \
--to=corbet@lwn.net \
--cc=arch0.zheng@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@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