Linux Power Management development
 help / color / mirror / Atom feed
From: Tomasz Wolski <tomasz.wolski@fujitsu.com>
To: icheng@nvidia.com
Cc: alison.schofield@intel.com, ardb@kernel.org,
	benjamin.cheatham@amd.com, dan.j.williams@intel.com,
	dave.jiang@intel.com, jonathan.cameron@huawei.com,
	linux-cxl@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
	nvdimm@lists.linux.dev, smita.koralahallichannabasappa@amd.com,
	tomasz.wolski@fujitsu.com
Subject: Re: [PATCH] dax/bus: Upgrade resource conflict message to dev_err() in alloc_dax_region()
Date: Tue, 19 May 2026 10:15:06 +0200	[thread overview]
Message-ID: <20260519081506.17283-1-tomasz.wolski@fujitsu.com> (raw)
In-Reply-To: <agWfgLxDeu_duejj@MWDK4CY14F>

Hello Richard,

Thanks for your feedback

>> Did you run into any kind of error or even machine crashing from this ?
No, I haven't hit this error path in practice. On systems I've tested, the deferral logic 
in hmem_register_cxl_device() correctly drops ranges that CXL claims

>> btw, though I am not against the change, I don't think this is a fix, maybe you can consider to remove the Fixes tag.
Agreed, I'll drop the tag in v2.

Best regards,
Tomasz

  reply	other threads:[~2026-05-19  8:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-14  9:32 [PATCH] dax/bus: Upgrade resource conflict message to dev_err() in alloc_dax_region() Tomasz Wolski
2026-05-14 10:13 ` Richard Cheng
2026-05-19  8:15   ` Tomasz Wolski [this message]
2026-05-14 16:41 ` Alison Schofield
2026-05-19  8:25   ` Tomasz Wolski

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=20260519081506.17283-1-tomasz.wolski@fujitsu.com \
    --to=tomasz.wolski@fujitsu.com \
    --cc=alison.schofield@intel.com \
    --cc=ardb@kernel.org \
    --cc=benjamin.cheatham@amd.com \
    --cc=dan.j.williams@intel.com \
    --cc=dave.jiang@intel.com \
    --cc=icheng@nvidia.com \
    --cc=jonathan.cameron@huawei.com \
    --cc=linux-cxl@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=nvdimm@lists.linux.dev \
    --cc=smita.koralahallichannabasappa@amd.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