From: Matthew Wilcox <willy@infradead.org>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] tools: Fix math.h breakage
Date: Tue, 30 Nov 2021 15:07:12 +0000 [thread overview]
Message-ID: <YaY+IFrgBOUGomW6@casper.infradead.org> (raw)
In-Reply-To: <YaY3hKLejcy09bZk@smile.fi.intel.com>
On Tue, Nov 30, 2021 at 04:39:00PM +0200, Andy Shevchenko wrote:
> On Tue, Nov 30, 2021 at 02:13:16PM +0000, Matthew Wilcox (Oracle) wrote:
> > Commit 98e1385ef24b broke the radix tree test suite in two different ways;
> > first by including math.h which didn't exist in the tools directory, and
> > second by removing an implicit include of spinlock.h before lockdep.h.
> > Fix both issues.
>
> Sorry for that and thank you for the fix.
> Acked-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
>
> I'm wondering if there is a way of not copying kernel headers manually,
> otherwise we always will have such breakages.
It's not necessarily that these are _copies_ of kernel headers, so much as
they're ways of mocking kernel interfaces when building userspace code.
We could separate out pieces and include them from each direction, but
that has its own problems, and doesn't necessarily solve these kinds of
problems either.
I think the only way to prevent these kinds of breakages is to make sure
the build bots are also building things.
next prev parent reply other threads:[~2021-11-30 15:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-30 14:13 Matthew Wilcox (Oracle)
2021-11-30 14:39 ` Andy Shevchenko
2021-11-30 15:07 ` Matthew Wilcox [this message]
2021-11-30 15:22 ` Andy Shevchenko
2021-11-30 15:23 ` Andy Shevchenko
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=YaY+IFrgBOUGomW6@casper.infradead.org \
--to=willy@infradead.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/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®