From: Greg KH <gregkh@linuxfoundation.org>
To: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
Cc: Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
Geert Uytterhoeven <geert+renesas@glider.be>
Subject: Re: [PATCH v2] docs: driver-model: Update the documentation for device class
Date: Wed, 21 Apr 2021 08:23:51 +0200 [thread overview]
Message-ID: <YH/E90QVq7yP01ii@kroah.com> (raw)
In-Reply-To: <20210421061340.GA6522@thinkpad>
On Wed, Apr 21, 2021 at 11:43:40AM +0530, Manivannan Sadhasivam wrote:
> On Tue, Apr 20, 2021 at 04:29:24PM -0600, Jonathan Corbet wrote:
> > Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org> writes:
> >
> > > The current documentation about the device class is out of date such
> > > that it refers to non-existent APIs and structures. This commit updates
> > > them to the current device class APIs and structures, removes wordings
> > > that no longer valid while trying to keep the original content intact.
> > >
> > > Signed-off-by: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
> > > ---
> > >
> > > Changes in v2:
> > >
> > > * Fixed CLASS_ATTR_RW as spotted by Greg
> > >
> > > .../driver-api/driver-model/class.rst | 144 ++++++++----------
> > > 1 file changed, 66 insertions(+), 78 deletions(-)
> >
> > Note that this file was removed in commit 1364c6787525 back in
> > February by Geert (added to CC). If you want to update this document,
> > you'll first want to bring it back.
> >
>
> Oh thanks for the info! Perhaps I could just revert 1364c6787525 and add this
> commit on top?
Nah, leave it removed for now, it needs lots of work to be relevant.
greg k-h
prev parent reply other threads:[~2021-04-21 6:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-07 6:10 [PATCH v2] docs: driver-model: Update the documentation for device class Manivannan Sadhasivam
2021-04-20 22:29 ` Jonathan Corbet
2021-04-21 6:13 ` Manivannan Sadhasivam
2021-04-21 6:23 ` Greg KH [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=YH/E90QVq7yP01ii@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=corbet@lwn.net \
--cc=geert+renesas@glider.be \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manivannan.sadhasivam@linaro.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).