linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Lukas Wunner <lukas@wunner.de>
Cc: "Rafael J. Wysocki" <rafael@kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Mauro Carvalho Chehab <mchehab@osg.samsung.com>,
	linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
	iommu@lists.linux-foundation.org,
	linux-samsung-soc@vger.kernel.org
Subject: Re: [PATCH 1/2] Documentation/core-api/device_link: Add initial documentation
Date: Mon, 5 Dec 2016 14:15:28 -0700	[thread overview]
Message-ID: <20161205141528.1c0e9f52@lwn.net> (raw)
In-Reply-To: <f5b568e349aaeb31039a0c4d01fdb05d8b3bdd2a.1480849144.git.lukas@wunner.de>

On Sun, 4 Dec 2016 13:10:04 +0100
Lukas Wunner <lukas@wunner.de> wrote:

> Document device links as introduced in v4.10 with commits:
>     4bdb35506b89 ("driver core: Add a wrapper around
>                    __device_release_driver()")
>     9ed9895370ae ("driver core: Functional dependencies tracking
>                    support")
>     8c73b4288496 ("PM / sleep: Make async suspend/resume of devices use
>                    device links")
>     21d5c57b3726 ("PM / runtime: Use device links")
>     baa8809f6097 ("PM / runtime: Optimize the use of device links")

I went ahead and applied this one to docs-next.  I did, however, take the
liberty of shifting it over to the driver-api manual.

Thanks,

jon

  parent reply	other threads:[~2016-12-05 21:15 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <cover.1480849144.git.lukas@wunner.de>
2016-12-05 12:03 ` [PATCH 0/2] Device links documentation Mauro Carvalho Chehab
     [not found] ` <a1c7a93ee8ef057fb70aa3abeed38daf989444fc.1480849144.git.lukas@wunner.de>
2016-12-05 12:20   ` [PATCH 2/2] driver core: Silence device links sphinx warning Mauro Carvalho Chehab
     [not found]     ` <20161205102030.2abae2b5-ch4gOOMV7nf/PtFMR13I2A@public.gmane.org>
2016-12-05 12:44       ` Lukas Wunner
     [not found]         ` <20161205124449.GA7539-JFq808J9C/izQB+pC5nmwQ@public.gmane.org>
2016-12-05 12:57           ` Mauro Carvalho Chehab
     [not found]   ` <a1c7a93ee8ef057fb70aa3abeed38daf989444fc.1480849144.git.lukas-JFq808J9C/izQB+pC5nmwQ@public.gmane.org>
2016-12-05 13:59     ` Greg Kroah-Hartman
2016-12-05 22:21   ` Rafael J. Wysocki
2016-12-05 13:09 ` [PATCH 0/2] Device links documentation Jonathan Corbet
     [not found] ` <f5b568e349aaeb31039a0c4d01fdb05d8b3bdd2a.1480849144.git.lukas@wunner.de>
2016-12-05 12:07   ` [PATCH 1/2] Documentation/core-api/device_link: Add initial documentation Mauro Carvalho Chehab
2016-12-05 13:05     ` Jonathan Corbet
     [not found]       ` <20161205060507.6bd6e944-T1hC0tSOHrs@public.gmane.org>
2016-12-05 13:36         ` Mauro Carvalho Chehab
2016-12-05 21:15   ` Jonathan Corbet [this message]
     [not found]   ` <f5b568e349aaeb31039a0c4d01fdb05d8b3bdd2a.1480849144.git.lukas-JFq808J9C/izQB+pC5nmwQ@public.gmane.org>
2016-12-06  1:41     ` Luis R. Rodriguez
2016-12-07 11:50       ` Lukas Wunner

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=20161205141528.1c0e9f52@lwn.net \
    --to=corbet@lwn.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=iommu@lists.linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=lukas@wunner.de \
    --cc=mchehab@osg.samsung.com \
    --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;
as well as URLs for NNTP newsgroup(s).