From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Ira Weiny <ira.weiny@intel.com>
Cc: Nathan Chancellor <nathan@kernel.org>,
Davidlohr Bueso <dave@stgolabs.net>,
Jonathan Cameron <jonathan.cameron@huawei.com>,
Dave Jiang <dave.jiang@intel.com>,
Alison Schofield <alison.schofield@intel.com>,
Vishal Verma <vishal.l.verma@intel.com>,
Dan Williams <dan.j.williams@intel.com>,
linux-cxl@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] cxl: Include range.h in cxl.h
Date: Tue, 1 Jul 2025 22:14:06 +0300 [thread overview]
Message-ID: <aGQzfh-36CnS_Jxg@smile.fi.intel.com> (raw)
In-Reply-To: <6864095bc5ecd_30815d2948c@iweiny-mobl.notmuch>
On Tue, Jul 01, 2025 at 11:14:19AM -0500, Ira Weiny wrote:
> Nathan Chancellor wrote:
> > On Tue, Jul 01, 2025 at 10:20:22AM -0500, Ira Weiny wrote:
> > > Nathan Chancellor wrote:
> > > > After commit aefeb286b960 ("libnvdimm: Don't use "proxy" headers"),
> > > > range.h may not be implicitly included, resulting in a build error:
> > >
> > > That said, I'm not seeing this issue. What config caught this?
> >
> > Fedora's aarch64 configuration [1] is where I initially noticed this.
> > Fedora's rpm site seems to be under the weather for me but I have it
> > mirrored [2] for my own test setup.
>
> Ah, I suspected it was a non-x86 build.
>
> Reviewed-by: Ira Weiny <ira.weiny@intel.com>
>
> Dave, I'll pull this in right now.
Thanks, I haven't seen issues and 0-day haven't given any (bad) report so far.
> > [1]: https://src.fedoraproject.org/rpms/kernel/raw/rawhide/f/kernel-aarch64-fedora.config
> > [2]: https://github.com/nathanchance/llvm-kernel-testing/raw/refs/heads/main/configs/fedora/aarch64.config
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2025-07-01 19:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-01 14:33 [PATCH] cxl: Include range.h in cxl.h Nathan Chancellor
2025-07-01 15:03 ` Jonathan Cameron
2025-07-01 15:10 ` Dave Jiang
2025-07-01 15:20 ` Ira Weiny
2025-07-01 15:38 ` Nathan Chancellor
2025-07-01 16:14 ` Ira Weiny
2025-07-01 19:14 ` Andy Shevchenko [this message]
2025-07-01 16:21 ` Ira Weiny
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=aGQzfh-36CnS_Jxg@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=alison.schofield@intel.com \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=dave@stgolabs.net \
--cc=ira.weiny@intel.com \
--cc=jonathan.cameron@huawei.com \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nathan@kernel.org \
--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