From: Chris Metcalf <cmetcalf@tilera.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: build failure after merge of the final tree (tile tree related)
Date: Tue, 24 May 2011 08:25:18 -0400 [thread overview]
Message-ID: <4DDBA3AE.6080608@tilera.com> (raw)
In-Reply-To: <20110524134203.62d859c0.sfr@canb.auug.org.au>
On 5/23/2011 11:42 PM, Stephen Rothwell wrote:
> Hi Chris,
>
> After merging the final tree, today's linux-next build (sparc64 defconfig)
> failed like this:
>
> [...]
>
> I added this patch for today:
>
> [...]
>
> diff --git a/include/linux/compat.h b/include/linux/compat.h
> index 644e1a4..ddcb7db 100644
> --- a/include/linux/compat.h
> +++ b/include/linux/compat.h
> @@ -13,6 +13,7 @@
> #include <linux/socket.h>
> #include <linux/if.h>
> #include <linux/fs.h>
> +#include <linux/aio_abi.h> /* for aio_context_t */
>
> #include <asm/compat.h>
> #include <asm/siginfo.h>
Stephen, thanks for the discovery and the fix. Apparently the uses in the
"tile" tree already happen to have this header included earlier, so I
didn't trip up against it. I'll take the change into my tree.
--
Chris Metcalf, Tilera Corp.
http://www.tilera.com
WARNING: multiple messages have this Message-ID (diff)
From: Chris Metcalf <cmetcalf@tilera.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: <linux-next@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: build failure after merge of the final tree (tile tree related)
Date: Tue, 24 May 2011 08:25:18 -0400 [thread overview]
Message-ID: <4DDBA3AE.6080608@tilera.com> (raw)
In-Reply-To: <20110524134203.62d859c0.sfr@canb.auug.org.au>
On 5/23/2011 11:42 PM, Stephen Rothwell wrote:
> Hi Chris,
>
> After merging the final tree, today's linux-next build (sparc64 defconfig)
> failed like this:
>
> [...]
>
> I added this patch for today:
>
> [...]
>
> diff --git a/include/linux/compat.h b/include/linux/compat.h
> index 644e1a4..ddcb7db 100644
> --- a/include/linux/compat.h
> +++ b/include/linux/compat.h
> @@ -13,6 +13,7 @@
> #include <linux/socket.h>
> #include <linux/if.h>
> #include <linux/fs.h>
> +#include <linux/aio_abi.h> /* for aio_context_t */
>
> #include <asm/compat.h>
> #include <asm/siginfo.h>
Stephen, thanks for the discovery and the fix. Apparently the uses in the
"tile" tree already happen to have this header included earlier, so I
didn't trip up against it. I'll take the change into my tree.
--
Chris Metcalf, Tilera Corp.
http://www.tilera.com
next prev parent reply other threads:[~2011-05-24 12:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-24 3:42 linux-next: build failure after merge of the final tree (tile tree related) Stephen Rothwell
2011-05-24 12:25 ` Chris Metcalf [this message]
2011-05-24 12:25 ` Chris Metcalf
-- strict thread matches above, loose matches on Subject: below --
2010-06-07 4:01 Stephen Rothwell
2010-06-07 12:56 ` Chris Metcalf
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=4DDBA3AE.6080608@tilera.com \
--to=cmetcalf@tilera.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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.