linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Grzegorz Jaszczyk <jaz@semihalf.com>,
	linux-kernel@vger.kernel.org, rafael@kernel.org
Cc: dmy@semihalf.com, tn@semihalf.com, dbehr@google.com,
	zide.chen@intel.corp-partner.google.com, seanjc@google.com,
	upstream@semihalf.com, hdegoede@redhat.com, markgross@kernel.org,
	dtor@google.com, mario.limonciello@amd.com,
	linux-pm@vger.kernel.org, x86@kernel.org,
	platform-driver-x86@vger.kernel.org,
	Grzegorz Jaszczyk <jaz@semihalf.com>
Subject: Re: [RESEND RFCv2 1/1] platform/x86: Add virtual PMC driver used for S2Idle
Date: Thu, 09 Feb 2023 19:05:09 +0100	[thread overview]
Message-ID: <87ttzu1zqi.ffs@tglx> (raw)
In-Reply-To: <20230209152123.3186930-2-jaz@semihalf.com>

On Thu, Feb 09 2023 at 15:21, Grzegorz Jaszczyk wrote:
> +
> +static struct acpi_s2idle_dev_ops amd_pmc_s2idle_dev_ops = {

What is AMD specific about this?

> +	.check = virt_pmc_s2idle_notify,
> +};

...

> +
> +MODULE_DESCRIPTION("Virtual PMC Driver");

Lacks MODULE_LICENSE("GPL")

Thanks,

        tglx

  reply	other threads:[~2023-02-09 18:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-09 15:21 [RESEND RFCv2 0/1] x86: allow to notify host about guest entering s2idle Grzegorz Jaszczyk
2023-02-09 15:21 ` [RESEND RFCv2 1/1] platform/x86: Add virtual PMC driver used for S2Idle Grzegorz Jaszczyk
2023-02-09 18:05   ` Thomas Gleixner [this message]
2023-02-10 10:51     ` Grzegorz Jaszczyk
2023-02-09 18:25   ` Limonciello, Mario
2023-02-10 10:56     ` Grzegorz Jaszczyk
2023-02-09 21:26   ` Sean Christopherson
2023-02-10 10:58     ` Grzegorz Jaszczyk

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=87ttzu1zqi.ffs@tglx \
    --to=tglx@linutronix.de \
    --cc=dbehr@google.com \
    --cc=dmy@semihalf.com \
    --cc=dtor@google.com \
    --cc=hdegoede@redhat.com \
    --cc=jaz@semihalf.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=mario.limonciello@amd.com \
    --cc=markgross@kernel.org \
    --cc=platform-driver-x86@vger.kernel.org \
    --cc=rafael@kernel.org \
    --cc=seanjc@google.com \
    --cc=tn@semihalf.com \
    --cc=upstream@semihalf.com \
    --cc=x86@kernel.org \
    --cc=zide.chen@intel.corp-partner.google.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).