From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: ira.weiny@intel.com
Cc: Jonathan Corbet <corbet@lwn.net>,
Dan Williams <dan.j.williams@intel.com>,
linux-kernel@vger.kernel.org, Dave Jiang <dave.jiang@intel.com>,
linux-doc@vger.kernel.org
Subject: Re: [PATCH 0/3] Improve Auxiliary Device documentation
Date: Wed, 3 Nov 2021 08:58:34 +0100 [thread overview]
Message-ID: <YYJBKrTlaqPfVYiJ@kroah.com> (raw)
In-Reply-To: <20211102215317.3676782-1-ira.weiny@intel.com>
On Tue, Nov 02, 2021 at 02:53:14PM -0700, ira.weiny@intel.com wrote:
> From: Ira Weiny <ira.weiny@intel.com>
>
> The auxiliary device documentation was not wrong but it was a bit difficult to
> follow. Add clarifications to ensure that details are not missed.
>
>
> Ira Weiny (3):
> Documentation/auxiliary_bus: Clarify auxiliary_device creation
> Documentation/auxiliary_bus: Clarify match_name
> Documentation/auxiliary_bus: Update Auxiliary device lifespan
>
> Documentation/driver-api/auxiliary_bus.rst | 136 ++++++++++++++++-----
Any chance that we can move this documentation into the .c file itself
to make it easier to maintain and keep up to date over time? I think
the v4l2 and drm subsystems do this pretty well, right?
thanks,
greg k-h
prev parent reply other threads:[~2021-11-03 7:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-02 21:53 [PATCH 0/3] Improve Auxiliary Device documentation ira.weiny
2021-11-02 21:53 ` [PATCH 1/3] Documentation/auxiliary_bus: Clarify auxiliary_device creation ira.weiny
2021-11-02 22:06 ` Jonathan Corbet
2021-11-02 22:53 ` [PATCH v2] " ira.weiny
2021-11-26 16:16 ` Greg Kroah-Hartman
2021-11-28 5:32 ` Ira Weiny
2021-11-28 7:59 ` Greg Kroah-Hartman
2021-11-02 21:53 ` [PATCH 2/3] Documentation/auxiliary_bus: Clarify match_name ira.weiny
2021-11-02 21:53 ` [PATCH 3/3] Documentation/auxiliary_bus: Update Auxiliary device lifespan ira.weiny
2021-11-03 7:58 ` Greg Kroah-Hartman [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=YYJBKrTlaqPfVYiJ@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=corbet@lwn.net \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=ira.weiny@intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@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.