linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bart Van Assche <Bart.VanAssche@wdc.com>
To: "rafael@kernel.org" <rafael@kernel.org>
Cc: "jejb@linux.vnet.ibm.com" <jejb@linux.vnet.ibm.com>,
	"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
	"terraluna977@gmail.com" <terraluna977@gmail.com>,
	"stern@rowland.harvard.edu" <stern@rowland.harvard.edu>,
	"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
	"martin.petersen@oracle.com" <martin.petersen@oracle.com>,
	"rjw@rjwysocki.net" <rjw@rjwysocki.net>
Subject: Re: [PATCH 1/2] PM / sleep: Make lock/unlock_system_sleep() available to kernel modules
Date: Fri, 5 Jan 2018 23:32:19 +0000	[thread overview]
Message-ID: <1515195138.3254.26.camel@wdc.com> (raw)
In-Reply-To: <CAJZ5v0igct51CSp6FB=s3OZyr5fKKMxvy=T7gg2L39=r72Jtbg@mail.gmail.com>

On Sat, 2018-01-06 at 00:00 +0100, Rafael J. Wysocki wrote:
> The changes are fine by me, but I really would prefer them to go in
> via the PM tree which I guess means that the second patch would need
> to go in this way too.

Hello Rafael,

If I can get a Tested-by from Woody and an Acked-by from Martin then I can
do that.

Thanks,

Bart.

  reply	other threads:[~2018-01-05 23:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-05 17:19 [PATCH 0/2] Fix a race condition between SPI domain validation and system suspend Bart Van Assche
2018-01-05 17:19 ` [PATCH 1/2] PM / sleep: Make lock/unlock_system_sleep() available to kernel modules Bart Van Assche
2018-01-05 23:00   ` Rafael J. Wysocki
2018-01-05 23:32     ` Bart Van Assche [this message]
2018-01-05 23:38       ` Rafael J. Wysocki
2018-01-05 17:19 ` [PATCH 2/2] Fix a race condition between SPI domain validation and system suspend Bart Van Assche
2018-01-08 16:02   ` Martin K. Petersen
2018-01-09  0:27     ` Rafael J. Wysocki

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=1515195138.3254.26.camel@wdc.com \
    --to=bart.vanassche@wdc.com \
    --cc=jejb@linux.vnet.ibm.com \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=rafael@kernel.org \
    --cc=rjw@rjwysocki.net \
    --cc=stern@rowland.harvard.edu \
    --cc=terraluna977@gmail.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;
as well as URLs for NNTP newsgroup(s).