mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alison Schofield <alison.schofield@intel.com>
To: Tomasz Wolski <tomasz.wolski@fujitsu.com>
Cc: <djbw@kernel.org>, <ardb@kernel.org>, <benjamin.cheatham@amd.com>,
	<dan.j.williams@intel.com>, <dave.jiang@intel.com>,
	<icheng@nvidia.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>
Subject: Re: [PATCH v2] dax/bus: Upgrade resource conflict message to dev_err() in alloc_dax_region()
Date: Wed, 27 May 2026 11:44:23 -0700	[thread overview]
Message-ID: <ahc7h8zMaTW2XUMU@aschofie-mobl2.lan> (raw)
In-Reply-To: <20260527080328.12171-1-tomasz.wolski@fujitsu.com>

On Wed, May 27, 2026 at 10:03:28AM +0200, Tomasz Wolski wrote:
> Hello Dan & Alison,
> 
> Thanks for your remarks
> 
> >> Just report the request_resource() failure. This case does not warrant exporting request_resource _conflict(). Historically one driver can not mess with another driver's resource beyond conflict detection.
> Do you think v1 of the patch is good enough or v3 is needed? (which in fact would be the same as v1)

Hi Tomasz,

As the person who caused the churn, I sympathize w you, but
as the person who will likely merge this, please send a v3 that
removes the Fixes tag, which was the other change in v2.

It'll keep the history cleaner.

Thanks!
Alison

> 
> Best regards,
> Tomasz

  reply	other threads:[~2026-05-27 18:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-19 10:18 Tomasz Wolski
2026-05-19 11:31 ` Jonathan Cameron
2026-05-19 23:27   ` Richard Cheng
2026-05-20  0:14 ` kernel test robot
2026-05-20  2:48   ` Alison Schofield
2026-05-20  3:56 ` Dan Williams
2026-05-27  8:03   ` Tomasz Wolski
2026-05-27 18:44     ` Alison Schofield [this message]
2026-05-28  6:40       ` 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=ahc7h8zMaTW2XUMU@aschofie-mobl2.lan \
    --to=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=djbw@kernel.org \
    --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 \
    --cc=tomasz.wolski@fujitsu.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
all inboxes | Powered by JetHome®