All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Nirmal Patel <nirmal.patel@linux.intel.com>
Cc: nirmal.patel@intel.com, linux-pci@vger.kernel.org,
	bhelgaas@google.com, kwilczynski@kernel.org, mani@kernel.org,
	robh@kernel.org, lpieralisi@kernel.org
Subject: Re: [PATCH] PCI: vmd: Only assign _OSC features in bare metal OS.
Date: Mon, 29 Jun 2026 20:18:31 +0300	[thread overview]
Message-ID: <akKo5w359FZU3uDU@ashevche-desk.local> (raw)
In-Reply-To: <20260629170243.269830-1-nirmal.patel@linux.intel.com>

On Mon, Jun 29, 2026 at 05:02:43PM +0000, Nirmal Patel wrote:

> Copy valid _OSC flags from root bridge only when OS can provide correct
> values. In virtual machine, all of the control features are disabled as
> hypervisor will not passthrough root bridge information to VM.

> Reviewed-by:  Andy Shevchenko <andriy.shevchenko@intel.com>

I confirm that I reviewed this internally and agree on the main approach and
the implementation. I think it's a redundant period in the Subject slipped,
but it maybe tweaked whilst applying I think.

-- 
With Best Regards,
Andy Shevchenko



  parent reply	other threads:[~2026-06-29 17:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-29 17:02 [PATCH] PCI: vmd: Only assign _OSC features in bare metal OS Nirmal Patel
2026-06-29 17:13 ` sashiko-bot
2026-06-29 17:18 ` Andy Shevchenko [this message]
2026-06-30 17:10 ` Bjorn Helgaas
2026-07-06 14:56   ` Nirmal Patel
2026-07-06 16:15   ` Manivannan Sadhasivam
  -- strict thread matches above, loose matches on Subject: below --
2026-06-29 17:01 Nirmal Patel
2026-06-29 17:11 ` sashiko-bot

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=akKo5w359FZU3uDU@ashevche-desk.local \
    --to=andriy.shevchenko@intel.com \
    --cc=bhelgaas@google.com \
    --cc=kwilczynski@kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=lpieralisi@kernel.org \
    --cc=mani@kernel.org \
    --cc=nirmal.patel@intel.com \
    --cc=nirmal.patel@linux.intel.com \
    --cc=robh@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.