linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rafael@kernel.org>
To: Artem Bityutskiy <dedekind1@gmail.com>
Cc: "Rafael J. Wysocki" <rafael@kernel.org>,
	x86@kernel.org, Thomas Gleixner <tglx@linutronix.de>,
	Linux PM Mailing List <linux-pm@vger.kernel.org>,
	Arjan van de Ven <arjan@linux.intel.com>
Subject: Re: [PATCH v4 0/4] Sapphire Rapids C0.x idle states support
Date: Wed, 13 Sep 2023 14:55:38 +0200	[thread overview]
Message-ID: <CAJZ5v0j2UF+UbHuYiSaemHRHgyWkvom5m=JQPwNTgkzdxpUcMg@mail.gmail.com> (raw)
In-Reply-To: <81abd4de9da3a8e93c80ef67127323e03cf779a0.camel@gmail.com>

On Wed, Sep 13, 2023 at 2:49 PM Artem Bityutskiy <dedekind1@gmail.com> wrote:
>
> On Wed, 2023-09-13 at 14:34 +0200, Rafael J. Wysocki wrote:
> > On Wed, Sep 13, 2023 at 1:37 PM Artem Bityutskiy <dedekind1@gmail.com> wrote:
> > >
> > > On Mon, 2023-08-28 at 19:43 +0300, Artem Bityutskiy wrote:
> > > > Hi,
> > > >
> > > > On Mon, 2023-07-10 at 12:30 +0300, Artem Bityutskiy wrote:
> > > >
> > > > > Artem Bityutskiy (4):
> > > > >   x86/umwait: use 'IS_ENABLED()'
> > > > >   x86/mwait: Add support for idle via umwait
> > > >
> > > > If these 2 patches are OK now, is there a chance to get them merged?
> > >
> > > Hi, I wonder if these 2 patches have any chances to get merged?
> > >
> > > May be there is something I am expected to do have not done? If so, please,
> > > accept my apologies and give me a direction.
> >
> > I think that they were based on the Arjan\s changes that got dropped.
> > If so, they need to be rebased and resent.
>
> The above quoted 2 patches are x86 bits, they introduce the basic umwait
> primitives. They are not based on Arjan's patches. They still apply cleanly, and
> do not need a refresh, as far as I can see.
>
> I was hoping to get arch/x86 bits merged.

This is up to the x86 maintainers, then.

> Then I would send the refreshed version of the intel_idle patches.

Well, if the x86 changes are only needed because of the subsequent
intel_idle changes, it may be still better to send a new version of
the whole patchset.

      reply	other threads:[~2023-09-13 12:55 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-10  9:30 [PATCH v4 0/4] Sapphire Rapids C0.x idle states support Artem Bityutskiy
2023-07-10  9:30 ` [PATCH v4 1/4] x86/umwait: use 'IS_ENABLED()' Artem Bityutskiy
2023-07-10  9:30 ` [PATCH v4 2/4] x86/mwait: Add support for idle via umwait Artem Bityutskiy
2023-07-10  9:30 ` [PATCH v4 3/4] intel_idle: rename 'intel_idle_hlt_irq_on()' Artem Bityutskiy
2023-07-14 15:34   ` Rafael J. Wysocki
2023-07-14 15:39     ` Arjan van de Ven
2023-07-14 18:11     ` Artem Bityutskiy
2023-07-14 21:01     ` Peter Zijlstra
2023-07-14 21:02       ` Arjan van de Ven
2023-07-14 21:12         ` Peter Zijlstra
2023-07-10  9:31 ` [PATCH v4 4/4] intel_idle: add C0.2 state for Sapphire Rapids Xeon Artem Bityutskiy
2023-07-20 18:35 ` [PATCH v4 0/4] Sapphire Rapids C0.x idle states support Rafael J. Wysocki
2023-08-28 16:43 ` Artem Bityutskiy
2023-09-13 11:37   ` Artem Bityutskiy
2023-09-13 12:34     ` Rafael J. Wysocki
2023-09-13 12:49       ` Artem Bityutskiy
2023-09-13 12:55         ` Rafael J. Wysocki [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='CAJZ5v0j2UF+UbHuYiSaemHRHgyWkvom5m=JQPwNTgkzdxpUcMg@mail.gmail.com' \
    --to=rafael@kernel.org \
    --cc=arjan@linux.intel.com \
    --cc=dedekind1@gmail.com \
    --cc=linux-pm@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --cc=x86@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).