From: Jonathan Cameron <Jonathan.Cameron@huawei.com>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: Jonathan Cameron <jic23@kernel.org>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
<linux-iio@vger.kernel.org>, Paul Cercueil <paul@crapouillou.net>,
Lorenzo Bianconi <lorenzo@kernel.org>,
"Tomasz Duszynski" <tomasz.duszynski@octakon.com>,
Linux PM <linux-pm@vger.kernel.org>
Subject: Re: [PATCH 2/8] PM: core: Add NS varients of EXPORT[_GPL]_SIMPLE_DEV_PM_OPS and runtime pm equiv
Date: Fri, 1 Apr 2022 15:06:04 +0100 [thread overview]
Message-ID: <20220401150604.00007acc@huawei.com> (raw)
In-Reply-To: <CAJZ5v0j47Ub=kXU5ZB_JF35xwBtUuLCwiFyEw-+B=r5z-Ac78Q@mail.gmail.com>
On Thu, 31 Mar 2022 19:21:14 +0200
"Rafael J. Wysocki" <rafael@kernel.org> wrote:
> Hi Jonathan,
>
> On Wed, Mar 30, 2022 at 2:30 PM Jonathan Cameron
> <Jonathan.Cameron@huawei.com> wrote:
> >
> > On Tue, 1 Mar 2022 11:31:45 +0000
> > Jonathan Cameron <Jonathan.Cameron@Huawei.com> wrote:
> >
> > > On Mon, 28 Feb 2022 21:13:25 +0100
> > > "Rafael J. Wysocki" <rafael@kernel.org> wrote:
> > >
> > > > On Sun, Feb 27, 2022 at 12:39 PM Jonathan Cameron <jic23@kernel.org> wrote:
> > > > >
> > > > > On Mon, 21 Feb 2022 20:37:57 +0100
> > > > > "Rafael J. Wysocki" <rafael.j.wysocki@intel.com> wrote:
> > > > >
> > > > > Hi Rafael,
> > > > > > CC: linux-pm
> > > > >
> > > > > Oops. Stupid omission on my part, sorry about that!
> > > > >
> > > > > >
> > > > > > On 2/20/2022 7:15 PM, Jonathan Cameron wrote:
> > > > > > > From: Jonathan Cameron <Jonathan.Cameron@huawei.com>
> > > > > > >
> > > > > > > As more drivers start to use namespaces, we need to have varients of these
> > > > > > > useful macros that allow the export to be in a particular namespace.
> > > > > > >
> > > > > > > Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
> > > > > > > Cc: Paul Cercueil <paul@crapouillou.net>
> > > > > > > Cc: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
> > > > > >
> > > > > > I'd rather route this through linux-pm unless you have dependent changes.
> > > > >
> > > > > Ok.
> > > > >
> > > > > The kxsd9 patch (4) is dependent on other changes queued for
> > > > > the merge window in IIO. If we want to do it through linux-pm I'd
> > > > > love it if we can manage to get the ground work in for the coming merge window.
> > > > >
> > > > > So options are:
> > > > >
> > > > > 1) This patch alone via linux-pm and I queue the users up for next cycle
> > > > > Fine by me but always awkward to have infrastructure with no users.
> > > > > 2) First 3 patches via linux-pm so we have a user (scd30) in a low churn
> > > > > driver and I'll queue the rest for 5.19. Fine by me as well.
> > > > > That goes on cleanly on 5.17-rc1 and there is nothing else in my review
> > > > > queue touching that driver.
> > > >
> > > > That would work for me.
> > >
> > > Great. Let's do that then. Are you fine picking them from this thread, or
> > > would you like me to resend with just those 3 patches as a fresh series?
> > Hi Rafael,
> >
> > I've not heard back from you, so have been assuming you'd pick those first
> > 3 patches up from this series. Is that a correct assumption?
>
> This was my intention, but then I lost track of them and now I can't
> find them in the linux-pm Patchwork. Sorry about this.
My fault, I think I forgot to cc linux-pm on the initial send and
you added it in your reply.
>
> Can you please resend just the 3 patches?
On their way.
>
> Thanks!
prev parent reply other threads:[~2022-04-01 14:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220220181522.541718-1-jic23@kernel.org>
[not found] ` <20220220181522.541718-3-jic23@kernel.org>
2022-02-21 19:37 ` [PATCH 2/8] PM: core: Add NS varients of EXPORT[_GPL]_SIMPLE_DEV_PM_OPS and runtime pm equiv Rafael J. Wysocki
2022-02-27 11:46 ` Jonathan Cameron
2022-02-28 20:13 ` Rafael J. Wysocki
2022-03-01 11:31 ` Jonathan Cameron
2022-03-30 12:30 ` Jonathan Cameron
2022-03-31 17:21 ` Rafael J. Wysocki
2022-04-01 14:06 ` Jonathan Cameron [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=20220401150604.00007acc@huawei.com \
--to=jonathan.cameron@huawei.com \
--cc=jic23@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=lorenzo@kernel.org \
--cc=paul@crapouillou.net \
--cc=rafael.j.wysocki@intel.com \
--cc=rafael@kernel.org \
--cc=tomasz.duszynski@octakon.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).