From: Guenter Roeck <linux@roeck-us.net>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Linux-Next <linux-next@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Vineet Gupta <vgupta@synopsys.com>,
Ulf Hansson <ulf.hansson@linaro.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux <linux@lists.openrisc.net>
Subject: Re: linux-next: New build failures in Sep 25 tree
Date: Thu, 25 Sep 2014 23:46:17 -0700 [thread overview]
Message-ID: <54250BB9.1020700@roeck-us.net> (raw)
In-Reply-To: <CAMuHMdXE4aU1qZ9iGBT48QfMv5v7gsBZSjL_1_D8p=JBJfeN6A@mail.gmail.com>
On 09/25/2014 11:30 PM, Geert Uytterhoeven wrote:
> Hi Günther,
>
> [cc openrisc]
>
> On Thu, Sep 25, 2014 at 10:25 PM, Guenter Roeck <linux@roeck-us.net> wrote:
>> New build failures:
>
>> openrisc-defconfig
>>
>> In file included from arch/openrisc/kernel/signal.c:31:0:
>> ./arch/openrisc/include/asm/syscall.h: In function 'syscall_get_arch':
>> ./arch/openrisc/include/asm/syscall.h:77:9: error: 'EM_OPENRISC' undeclared
>
> That's not a new one. It's been failing for half or year or so.
>
Thought I had seen it before.
> If you only see it now, that means something else got fixed ;-)
>
That's one way to put it ;-)
Guenter
WARNING: multiple messages have this Message-ID (diff)
From: Guenter Roeck <linux@roeck-us.net>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Linux-Next <linux-next@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Vineet Gupta <vgupta@synopsys.com>,
Ulf Hansson <ulf.hansson@linaro.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux <linux@openrisc.net>
Subject: Re: linux-next: New build failures in Sep 25 tree
Date: Thu, 25 Sep 2014 23:46:17 -0700 [thread overview]
Message-ID: <54250BB9.1020700@roeck-us.net> (raw)
In-Reply-To: <CAMuHMdXE4aU1qZ9iGBT48QfMv5v7gsBZSjL_1_D8p=JBJfeN6A@mail.gmail.com>
On 09/25/2014 11:30 PM, Geert Uytterhoeven wrote:
> Hi Günther,
>
> [cc openrisc]
>
> On Thu, Sep 25, 2014 at 10:25 PM, Guenter Roeck <linux@roeck-us.net> wrote:
>> New build failures:
>
>> openrisc-defconfig
>>
>> In file included from arch/openrisc/kernel/signal.c:31:0:
>> ./arch/openrisc/include/asm/syscall.h: In function 'syscall_get_arch':
>> ./arch/openrisc/include/asm/syscall.h:77:9: error: 'EM_OPENRISC' undeclared
>
> That's not a new one. It's been failing for half or year or so.
>
Thought I had seen it before.
> If you only see it now, that means something else got fixed ;-)
>
That's one way to put it ;-)
Guenter
next prev parent reply other threads:[~2014-09-26 6:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-25 20:25 linux-next: New build failures in Sep 25 tree Guenter Roeck
2014-09-26 2:23 ` Vineet Gupta
2014-09-26 6:30 ` Geert Uytterhoeven
2014-09-26 6:30 ` Geert Uytterhoeven
2014-09-26 6:46 ` Guenter Roeck [this message]
2014-09-26 6:46 ` Guenter Roeck
2014-09-26 7:59 ` Stefan Kristiansson
2014-09-26 7:59 ` Stefan Kristiansson
2014-09-26 13:32 ` Guenter Roeck
2014-09-26 13:32 ` Guenter Roeck
2014-09-26 15:08 ` Eric Paris
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=54250BB9.1020700@roeck-us.net \
--to=linux@roeck-us.net \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux@lists.openrisc.net \
--cc=sfr@canb.auug.org.au \
--cc=ulf.hansson@linaro.org \
--cc=vgupta@synopsys.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.