All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@nvidia.com>
To: Venkat Rao Bagalkote <venkat88@linux.ibm.com>
Cc: paulmck@kernel.org, Stephen Rothwell <sfr@canb.auug.org.au>,
	Dave Jiang <dave.jiang@intel.com>,
	Dan Williams <dan.j.williams@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,
	Madhavan Srinivasan <maddy@linux.ibm.com>
Subject: Re: [BUG -next] ./usr/include/cxl/features.h:11:10: fatal error: uuid/uuid.h: No such file or directory
Date: Wed, 2 Apr 2025 08:44:12 -0300	[thread overview]
Message-ID: <20250402114412.GA342109@nvidia.com> (raw)
In-Reply-To: <ce38cbe3-429d-466b-bc8c-7dbb7c596ab9@linux.ibm.com>

On Wed, Apr 02, 2025 at 11:57:04AM +0530, Venkat Rao Bagalkote wrote:
> > So the various kernel-build howtos will be updated?  Or is a patch
> > forthcoming?

I was going to pick up Dan's patch after the merge window closes

> FYI, now the issue is on the main line kernel also.

I thought the header test stuff was disabled now?? How are people
hitting this?

Jason

  reply	other threads:[~2025-04-02 11:44 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
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 [this message]
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=20250402114412.GA342109@nvidia.com \
    --to=jgg@nvidia.com \
    --cc=alison.schofield@intel.com \
    --cc=dan.j.williams@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=maddy@linux.ibm.com \
    --cc=paulmck@kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=venkat88@linux.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.