All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: "Rafael J . Wysocki" <rjw@rjwysocki.net>, Len Brown <lenb@kernel.org>
Cc: Sinan Kaya <okaya@kernel.org>,
	Yicong Yang <yangyicong@hisilicon.com>,
	Sean V Kelley <sean.v.kelley@intel.com>,
	linux-pci@vger.kernel.org, linux-acpi@vger.kernel.org,
	linux-kernel@vger.kernel.org, Bjorn Helgaas <bhelgaas@google.com>
Subject: [PATCH 0/3] PCI/ACPI: _OSC cleanups
Date: Tue, 26 Jan 2021 16:03:08 -0600	[thread overview]
Message-ID: <20210126220311.2925565-1-helgaas@kernel.org> (raw)

From: Bjorn Helgaas <bhelgaas@google.com>

Clean up a few _OSC-related things.

We talked about the _OSC failure message in the last patch long ago, and I
just dropped the ball, sorry about that.  Previous discussion:
https://lore.kernel.org/linux-pci/20200602223618.GA845676@bjorn-Precision-5520/

I'm happy to merge these given your ack, Rafael, or you can take them if
they look good to you.

Bjorn Helgaas (3):
  PCI/ACPI: Make acpi_pci_osc_control_set() static
  PCI/ACPI: Remove unnecessary osc_lock
  PCI/ACPI: Clarify message about _OSC failure

 drivers/acpi/pci_root.c | 40 ++++++++++++++--------------------------
 include/linux/acpi.h    |  3 ---
 2 files changed, 14 insertions(+), 29 deletions(-)

-- 
2.25.1


             reply	other threads:[~2021-01-27 12:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-26 22:03 Bjorn Helgaas [this message]
2021-01-26 22:03 ` [PATCH 1/3] PCI/ACPI: Make acpi_pci_osc_control_set() static Bjorn Helgaas
2021-01-26 22:03 ` [PATCH 2/3] PCI/ACPI: Remove unnecessary osc_lock Bjorn Helgaas
2021-01-26 22:03 ` [PATCH 3/3] PCI/ACPI: Clarify message about _OSC failure Bjorn Helgaas
2021-01-27 13:55 ` [PATCH 0/3] PCI/ACPI: _OSC cleanups Rafael J. Wysocki
2021-01-27 15:39   ` Bjorn Helgaas

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=20210126220311.2925565-1-helgaas@kernel.org \
    --to=helgaas@kernel.org \
    --cc=bhelgaas@google.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=okaya@kernel.org \
    --cc=rjw@rjwysocki.net \
    --cc=sean.v.kelley@intel.com \
    --cc=yangyicong@hisilicon.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 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.