Linux CXL
 help / color / mirror / Atom feed
From: Dan Williams <dan.j.williams@intel.com>
To: "Paul E. McKenney" <paulmck@kernel.org>,
	Dan Williams <dan.j.williams@intel.com>
Cc: Dave Jiang <dave.jiang@intel.com>, <linux-cxl@vger.kernel.org>,
	<dave@stgolabs.net>, <jonathan.cameron@huawei.com>,
	<alison.schofield@intel.com>, <vishal.l.verma@intel.com>,
	<ira.weiny@intel.com>, <gourry@gourry.net>,
	<linux-kernel@vger.kernel.org>, <linux-next@vger.kernel.org>,
	<sfr@canb.auug.org.au>
Subject: Re: [BUG -next] ./usr/include/cxl/features.h:11:10: fatal error: uuid/uuid.h: No such file or directory
Date: Fri, 28 Mar 2025 17:23:37 -0700	[thread overview]
Message-ID: <67e73d89dc6c4_201f029467@dwillia2-xfh.jf.intel.com.notmuch> (raw)
In-Reply-To: <fa4ee4e3-40f7-4e11-be14-7cd0b223def4@paulmck-laptop>

Paul E. McKenney wrote:
> On Fri, Mar 28, 2025 at 04:26:21PM -0700, Dan Williams wrote:
> > Paul E. McKenney wrote:
> > [..]
> > > > > Making the above change got me this:
> > > > > 
> > > > > usr/include/cxl/features.h:59:9: error: unknown type name ‘uuid_t’
> > > > I wasn't able to hit that with allmodconfig on x86 with a Fedora 41 build setup. What is the specific command lines you are using?
> > > 
> > > make clean
> > > make allmodconfig
> > > make -j$N
> > > 
> > > Though encapsulated as follows:
> > > 
> > > tools/testing/selftests/rcutorture/bin/torture.sh --do-none --do-allmodconfig
> > 
> > The problem is that uuid_t is not defined for uapi headers to reuse.
> > Perhaps checkpatch should be checking for uuid_t in uapi headers going
> > forward.
> 
> And for whatever it is worth, "git bisect" converged here:
> 
> 9b8e73cdb141 cxl: Move cxl feature command structs to user header

That makes sense because that was the point at which the usage of uuid_t
in those data structures became invalid.

I am going to have a firm talking to whomever added their Reviewed-by to
that... cue Michael Jackson's "I'm looking at the man in the mirror".

> > For now the following builds for me, but it is a quite a mess to undo
> > the assumption that that the hardware object definitions can not use
> > uuid_t:
> 
> Even better, this builds fine for me:
> 
> Tested-by: Paul E. McKenney <paulmck@kernel.org>
> 
> Thank you both!

Thanks for the bisect Paul!

  reply	other threads:[~2025-03-29  0:23 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-28 17:39 [BUG -next] ./usr/include/cxl/features.h:11:10: fatal error: uuid/uuid.h: No such file or directory Paul E. McKenney
2025-03-28 20:03 ` Dave Jiang
2025-03-28 20:45   ` Paul E. McKenney
2025-03-28 21:22     ` Dave Jiang
2025-03-28 21:57       ` Paul E. McKenney
2025-03-28 23:26         ` Dan Williams
2025-03-28 23:58           ` Paul E. McKenney
2025-03-29  0:23             ` Dan Williams [this message]
2025-03-29  0:26           ` Dave Jiang
2025-03-31 13:24             ` Jason Gunthorpe
2025-03-31 16:48               ` Paul E. McKenney
2025-03-31 16:54               ` Dan Williams
2025-03-31 17:17                 ` Jason Gunthorpe
2025-03-31 19:47                   ` Dan Williams
2025-04-01  7:01                     ` Venkat Rao Bagalkote
2025-04-01 14:08                       ` Paul E. McKenney
2025-04-01 15:15                       ` Dave Jiang
2025-04-02  0:07                         ` Paul E. McKenney
2025-04-02  0:18                           ` Dave Jiang
2025-04-02  0:47                             ` Stephen Rothwell
2025-04-02  4:21                               ` Paul E. McKenney
2025-04-02  6:27                                 ` Venkat Rao Bagalkote
2025-04-02 11:44                                   ` Jason Gunthorpe
2025-04-02 13:42                                     ` Venkat Rao Bagalkote
2025-04-02 17:20                                     ` Paul E. McKenney
2025-04-07 17:49                 ` Jason Gunthorpe
2025-04-05 17:34           ` Palmer Dabbelt

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=67e73d89dc6c4_201f029467@dwillia2-xfh.jf.intel.com.notmuch \
    --to=dan.j.williams@intel.com \
    --cc=alison.schofield@intel.com \
    --cc=dave.jiang@intel.com \
    --cc=dave@stgolabs.net \
    --cc=gourry@gourry.net \
    --cc=ira.weiny@intel.com \
    --cc=jonathan.cameron@huawei.com \
    --cc=linux-cxl@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=paulmck@kernel.org \
    --cc=sfr@canb.auug.org.au \
    --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