linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lukas Wunner <lukas@wunner.de>
To: Bjorn Helgaas <helgaas@kernel.org>, linux-pci@vger.kernel.org
Cc: Gregory Price <gregory.price@memverge.com>,
	Ira Weiny <ira.weiny@intel.com>,
	Jonathan Cameron <Jonathan.Cameron@huawei.com>,
	Dan Williams <dan.j.williams@intel.com>,
	Alison Schofield <alison.schofield@intel.com>,
	Vishal Verma <vishal.l.verma@intel.com>,
	"Li, Ming" <ming4.li@intel.com>,
	linux-cxl@vger.kernel.org
Subject: [PATCH 0/2] DOE WARN splat be gone
Date: Mon, 28 Nov 2022 05:15:50 +0100	[thread overview]
Message-ID: <cover.1669608950.git.lukas@wunner.de> (raw)

Here's my proposal to fix the DOE WARN splat reported by Gregory Price:

One backportable oneliner to replace INIT_WORK() with INIT_WORK_ONSTACK()
and one patch to change the API and thus fix the problem for good.

So that's an alternative approach to Ira's.

Please review and test.  Thanks!


Lukas Wunner (2):
  PCI/DOE: Silence WARN splat upon task submission
  PCI/DOE: Provide synchronous API

 drivers/cxl/core/pci.c  |  58 +++++++-------------
 drivers/pci/doe.c       | 114 +++++++++++++++++++++++++++++++++-------
 include/linux/pci-doe.h |  47 ++---------------
 3 files changed, 117 insertions(+), 102 deletions(-)

-- 
2.36.1


             reply	other threads:[~2022-11-28  4:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-28  4:15 Lukas Wunner [this message]
2022-11-28  4:25 ` [PATCH 1/2] PCI/DOE: Silence WARN splat upon task submission Lukas Wunner
2022-11-30 15:36   ` Jonathan Cameron
2022-11-30 18:52     ` Ira Weiny
2022-11-28  4:25 ` [PATCH 2/2] PCI/DOE: Provide synchronous API Lukas Wunner
2022-11-30 15:33   ` Jonathan Cameron
2022-11-30 18:50     ` Ira Weiny
2022-12-03 13:51     ` Lukas Wunner

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=cover.1669608950.git.lukas@wunner.de \
    --to=lukas@wunner.de \
    --cc=Jonathan.Cameron@huawei.com \
    --cc=alison.schofield@intel.com \
    --cc=dan.j.williams@intel.com \
    --cc=gregory.price@memverge.com \
    --cc=helgaas@kernel.org \
    --cc=ira.weiny@intel.com \
    --cc=linux-cxl@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=ming4.li@intel.com \
    --cc=vishal.l.verma@intel.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).