From: Heikki Krogerus <heikki.krogerus@linux.intel.com>
To: "Rafael J. Wysocki" <rafael@kernel.org>, Felipe Balbi <balbi@kernel.org>
Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
linux-acpi@vger.kernel.org
Subject: [PATCH 0/3] PM operations for software nodes
Date: Tue, 25 Aug 2020 16:59:48 +0300 [thread overview]
Message-ID: <20200825135951.53340-1-heikki.krogerus@linux.intel.com> (raw)
Hi guys,
Unfortunately the last patch depends on this:
https://lore.kernel.org/linux-usb/20200821131101.81915-1-heikki.krogerus@linux.intel.com/
Would it be easiest that Felipe took care of these (assuming they are
acceptable)?
thanks,
Heikki Krogerus (3):
software node: Power management operations for software nodes
software node: Introduce device_add_software_node()
usb: dwc3: pci: Register a software node for the dwc3 platform device
drivers/base/power/common.c | 8 +-
drivers/base/swnode.c | 569 +++++++++++++++++++++++++++++++++++-
drivers/usb/dwc3/dwc3-pci.c | 175 ++++++-----
include/linux/property.h | 13 +
4 files changed, 666 insertions(+), 99 deletions(-)
--
2.28.0
next reply other threads:[~2020-08-25 14:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-25 13:59 Heikki Krogerus [this message]
2020-08-25 13:59 ` [PATCH 1/3] software node: Power management operations for software nodes Heikki Krogerus
2020-09-25 15:54 ` Rafael J. Wysocki
2020-09-28 11:32 ` Heikki Krogerus
2020-08-25 13:59 ` [PATCH 2/3] software node: Introduce device_add_software_node() Heikki Krogerus
2020-08-25 14:32 ` Andy Shevchenko
2020-08-25 14:33 ` Andy Shevchenko
2020-08-25 13:59 ` [PATCH 3/3] usb: dwc3: pci: Register a software node for the dwc3 platform device Heikki Krogerus
2020-08-25 14:39 ` [PATCH 0/3] PM operations for software nodes Andy Shevchenko
2020-09-16 13:27 ` Heikki Krogerus
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=20200825135951.53340-1-heikki.krogerus@linux.intel.com \
--to=heikki.krogerus@linux.intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=balbi@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=sakari.ailus@linux.intel.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