From: Sudeep Holla <sudeep.holla@arm.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
Jisheng Zhang <jszhang@marvell.com>,
Steve Longerbeam <steve_longerbeam@mentor.com>,
Eugeniu Rosca <roscaeugeniu@gmail.com>,
Joshua Frkuska <joshua_frkuska@mentor.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Sudeep Holla <sudeep.holla@arm.com>
Subject: Re: [RFC PATCH] drivers core: cpu: add hotplug callback to update cpu_dev state to resumed
Date: Wed, 6 Feb 2019 13:59:09 +0000 [thread overview]
Message-ID: <20190206135909.GA24335@e107155-lin> (raw)
In-Reply-To: <2477683.mi0XWuPk1d@aspire.rjw.lan>
On Wed, Feb 06, 2019 at 11:31:04AM +0100, Rafael J. Wysocki wrote:
> On Monday, February 4, 2019 4:37:20 PM CET Sudeep Holla wrote:
> >
> > Sorry for the nag, since the title has RFC, thought there are chances of
> > this getting lost. Let me know if the below idea aligns with your suggestion ?
>
> RFC would be fine, but Patchwork doesn't pick up patches posted as replies
> in the middle of a thread. :-)
>
I completely understand and I had intentions to post it as a patch so
that patchwork sees it. Just wanted to check if I align well with what
you suggested.
> Yes, this is basically what I suggested, please post.
>
Thanks for confirming. I will post the patch shortly.
--
Regards,
Sudeep
prev parent reply other threads:[~2019-02-06 13:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-21 11:37 How to remove warn msg "cache: parent cpui should not be sleeping" i=1, 2, 3 Jisheng Zhang
2016-12-21 16:54 ` Sudeep Holla
2016-12-22 7:48 ` Jisheng Zhang
2018-08-20 17:46 ` Steve Longerbeam
2018-10-02 17:07 ` Eugeniu Rosca
2019-01-25 13:07 ` Eugeniu Rosca
2019-01-25 15:09 ` [RFC PATCH] drivers core: cpu: add hotplug callback to update cpu_dev state to resumed Sudeep Holla
2019-01-27 13:57 ` Eugeniu Rosca
2019-01-30 23:48 ` Rafael J. Wysocki
2019-01-31 16:05 ` Sudeep Holla
2019-02-04 15:37 ` Sudeep Holla
2019-02-04 15:44 ` Greg Kroah-Hartman
2019-02-04 15:52 ` Sudeep Holla
2019-02-06 10:31 ` Rafael J. Wysocki
2019-02-06 13:59 ` Sudeep Holla [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=20190206135909.GA24335@e107155-lin \
--to=sudeep.holla@arm.com \
--cc=gregkh@linuxfoundation.org \
--cc=joshua_frkuska@mentor.com \
--cc=jszhang@marvell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=roscaeugeniu@gmail.com \
--cc=steve_longerbeam@mentor.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).