From: David Daney <ddaney@caviumnetworks.com>
To: Sudip Mukherjee <sudipm.mukherjee@gmail.com>,
Ralf Baechle <ralf@linux-mips.org>
Cc: David Daney <david.daney@cavium.com>,
<linux-next@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
<kernel-testers@vger.kernel.org>
Subject: Re: linux-next: Tree for Feb 17
Date: Wed, 17 Feb 2016 09:37:44 -0800 [thread overview]
Message-ID: <56C4AFE8.6020101@caviumnetworks.com> (raw)
In-Reply-To: <20160217115248.GA4294@sudip-pc>
On 02/17/2016 03:52 AM, Sudip Mukherjee wrote:
> On Wed, Feb 17, 2016 at 04:39:21PM +1100, Stephen Rothwell wrote:
>> Hi all,
>>
>> Changes since 20160216:
>
> since last few days build of mips cavium_octeon_defconfig is failing
> with the error:
> arch/mips/include/asm/octeon/cvmx.h:60:39: fatal error:
> asm/octeon/cvmx-ciu3-defs.h: No such file or directory
>
When Ralf applied the patches, he missed this one:
https://www.linux-mips.org/cgi-bin/mesg.cgi?a=linux-mips&i=1455044413-9823-4-git-send-email-ddaney.cavm%40gmail.com
This is PATCH 3/8 and if applied in the proper order, it should fix
this problem.
Ralf: It looks like you should consider re-spinning mips-for-linux-next
to include this patch.
David.
> caused by commit:
> dfb354bef1fa ("MIPS: OCTEON: Add model checking support for cn73xx, cnf75xx and cn78xx")
>
> The #include for the header file is added but the header file is not in
> the tree.
>
> regards
> sudip
>
next prev parent reply other threads:[~2016-02-17 17:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-17 5:39 linux-next: Tree for Feb 17 Stephen Rothwell
2016-02-17 11:52 ` Sudip Mukherjee
2016-02-17 17:37 ` David Daney [this message]
2016-02-23 12:51 ` Sudip Mukherjee
-- strict thread matches above, loose matches on Subject: below --
2023-02-17 4:03 Stephen Rothwell
2022-02-17 9:51 Stephen Rothwell
2022-02-18 13:39 ` Mark Brown
2022-02-27 22:33 ` Stephen Rothwell
2021-02-17 12:42 Stephen Rothwell
2020-02-17 4:18 Stephen Rothwell
2017-02-17 5:49 Stephen Rothwell
2015-02-17 5:02 Stephen Rothwell
2014-02-17 6:23 Stephen Rothwell
2012-02-17 5:50 Stephen Rothwell
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=56C4AFE8.6020101@caviumnetworks.com \
--to=ddaney@caviumnetworks.com \
--cc=david.daney@cavium.com \
--cc=kernel-testers@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=ralf@linux-mips.org \
--cc=sfr@canb.auug.org.au \
--cc=sudipm.mukherjee@gmail.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 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 NNTP newsgroup(s).