From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Linux PM <linux-pm@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Mauro Carvalho Chehab <mchehab@osg.samsung.com>,
Linux Documentation <linux-doc@vger.kernel.org>
Subject: Re: [PATCH] PM / docs: Drop confusing kernel-doc references from infrastructure.rst
Date: Mon, 02 Jan 2017 23:39:17 +0100 [thread overview]
Message-ID: <2071156.SHKBpIhHlC@aspire.rjw.lan> (raw)
In-Reply-To: <20170102153920.56c48a83@lwn.net>
On Monday, January 02, 2017 03:39:20 PM Jonathan Corbet wrote:
> On Mon, 02 Jan 2017 23:05:31 +0100
> "Rafael J. Wysocki" <rjw@rjwysocki.net> wrote:
>
> > > From: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
> > >
> > > The references to drivers/base/power/main.c and
> > > drivers/acpi/scan.c from Documentation/driver-api/infrastructure.rst
> > > are confusing. They both cause descriptions of functions that are
> > > not relevant to device drivers at all to be generated and none of
> > > them is sufficient to cover the API in a meaningful way.
> > >
> > > Drop them for now.
> > >
> > > Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
> >
> > I'd like this to go into 4.10.
> >
> > Are there any objections here?
>
> None here. Sorry, somehow I failed to see this when I was putting
> together the fixes to send a few days ago. If you want to include it in
> a batch of yours, feel free to do so with my ack; otherwise I can ship it
> Linusward in a bit.
Thanks!
I'll be sending a PM pull request in a couple of days, so I'll include this one.
Cheers,
Rafael
prev parent reply other threads:[~2017-01-02 22:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-19 20:36 Rafael J. Wysocki
2017-01-02 22:05 ` Rafael J. Wysocki
2017-01-02 22:39 ` Jonathan Corbet
2017-01-02 22:39 ` Rafael J. Wysocki [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=2071156.SHKBpIhHlC@aspire.rjw.lan \
--to=rjw@rjwysocki.net \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mchehab@osg.samsung.com \
/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
all inboxes | Powered by JetHome®