From: Mike Frysinger <vapier@gentoo.org>
To: Joseph Myers <joseph@codesourcery.com>
Cc: libc-alpha@sourceware.org, Chung-Lin Tang <cltang@codesourcery.com>
Subject: Re: nios2 sys/cachectl.h includes nonexistent asm/cachectl.h
Date: Sun, 27 Nov 2016 07:14:00 -0000 [thread overview]
Message-ID: <20161127071412.GZ21655@vapier.lan> (raw)
In-Reply-To: <alpine.DEB.2.20.1611161845050.26593@digraph.polyomino.org.uk>
[-- Attachment #1: Type: text/plain, Size: 1001 bytes --]
On 16 Nov 2016 18:45, Joseph Myers wrote:
> On Tue, 15 Nov 2016, Mike Frysinger wrote:
> > On 04 Nov 2016 21:37, Joseph Myers wrote:
> > > nios2 glibc compile-only test results include:
> > >
> > > FAIL: misc/check-installed-headers-c
> > > FAIL: misc/check-installed-headers-cxx
> > >
> > > This is because sys/cachectl.h includes asm/cachectl.h, and the Linux
> > > kernel has no such header. How is this meant to work? Should that
> > > #include just be removed?
> >
> > delete it for now. looks like they speced it out for future usage,
> > but haven't yet gotten around to it. the kernel will explicitly
> > throw an error if the |op| field is non-zero.
>
> This patch does that.
>
> Do not include asm/cachectl.h in nios2 sys/cachectl.h.
>
> The nios2 sys/cachectl.h includes a kernel header asm/cachectl.h,
> which does not exist, so causing the check-installed-headers tests to
> fail. This patch removes the include of a nonexistent header.
lgtm
-mike
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2016-11-27 7:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-04 21:37 Joseph Myers
2016-11-16 5:31 ` Mike Frysinger
2016-11-16 18:45 ` Joseph Myers
2016-11-21 16:48 ` Ping " Joseph Myers
2016-11-27 7:14 ` Mike Frysinger [this message]
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=20161127071412.GZ21655@vapier.lan \
--to=vapier@gentoo.org \
--cc=cltang@codesourcery.com \
--cc=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).