From: Paul Burton <paul.burton@imgtec.com>
To: Jacek Anaszewski <j.anaszewski@samsung.com>
Cc: Ralf Baechle <ralf@linux-mips.org>, Bryan Wu <cooloney@gmail.com>,
Richard Purdie <rpurdie@rpsys.net>,
Markos Chandras <markos.chandras@imgtec.com>,
linux-leds@vger.kernel.org, linux-mips@linux-mips.org
Subject: Re: [PATCH v2] LED/MIPS: Move SEAD3 LED driver to where it belongs.
Date: Fri, 18 Sep 2015 14:05:49 -0700 [thread overview]
Message-ID: <20150918210549.GD16992@NP-P-BURTON> (raw)
In-Reply-To: <55FA7BA0.4080706@samsung.com>
On Thu, Sep 17, 2015 at 10:36:48AM +0200, Jacek Anaszewski wrote:
> Hi Ralf,
>
> This patch got stuck somewhere in my mailbox and just
> recently showed up to my eyes again, so I applied it to v4.3-rc1, but when
> tried to compile-test it, I got following errors:
>
> arch/mips/kernel/signal.c: In function 'sc_to_extcontext':
> arch/mips/kernel/signal.c:143:12: error: 'struct ucontext' has no member
> named 'uc_extcontext'
> return &uc->uc_extcontext;
> ^
<snip...>
> Compilation succeeds with v4.2-rc8.
> Is it a known issue?
Hi Jacek,
The patches adding the MSA extended context added a MIPS-specific
ucontext.h, where we were previously were using the generic one. Kbuild
doesn't automatically remove the old generated header that includes the
generic version, so could you try either cleaning your working tree or
removing arch/mips/include/generated and trying again?
Thanks,
Paul
next prev parent reply other threads:[~2015-09-18 21:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-03 15:04 [PATCH v2] LED/MIPS: Move SEAD3 LED driver to where it belongs Ralf Baechle
2015-08-03 15:33 ` Sergei Shtylyov
2015-08-04 12:18 ` Jacek Anaszewski
2015-09-17 8:36 ` Jacek Anaszewski
2015-09-18 21:05 ` Paul Burton [this message]
2015-09-19 2:49 ` Florian Fainelli
2015-09-21 8:52 ` Jacek Anaszewski
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=20150918210549.GD16992@NP-P-BURTON \
--to=paul.burton@imgtec.com \
--cc=cooloney@gmail.com \
--cc=j.anaszewski@samsung.com \
--cc=linux-leds@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=markos.chandras@imgtec.com \
--cc=ralf@linux-mips.org \
--cc=rpurdie@rpsys.net \
/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