From: Markos Chandras <Markos.Chandras@imgtec.com>
To: Reinoud Koornstra <reinoudkoornstra@gmail.com>
Cc: <linux-mips@linux-mips.org>
Subject: Re: compile failure linux 3.10 with gcc 4.9.3 for mips
Date: Thu, 16 Jul 2015 09:42:25 +0100 [thread overview]
Message-ID: <55A76E71.8090909@imgtec.com> (raw)
In-Reply-To: <CAAA5faHubPyT8D+QYB_M+qyCo-rRzPDO3fSH1HtSXCfCTj40HA@mail.gmail.com>
On 07/15/2015 08:56 PM, Reinoud Koornstra wrote:
> Thanks for your answer.
> Is this patch going in upstream
> Thanks,
>
> Reinoud
>
It's already upstream just not in 3.10. A more recent kernel should
compile fine with your toolchain.
--
markos
WARNING: multiple messages have this Message-ID (diff)
From: Markos Chandras <Markos.Chandras@imgtec.com>
To: Reinoud Koornstra <reinoudkoornstra@gmail.com>
Cc: linux-mips@linux-mips.org
Subject: Re: compile failure linux 3.10 with gcc 4.9.3 for mips
Date: Thu, 16 Jul 2015 09:42:25 +0100 [thread overview]
Message-ID: <55A76E71.8090909@imgtec.com> (raw)
Message-ID: <20150716084225.Fe0VKk0AkZKPWHGwr6AJG3jjTSg505fUReHNkUEZTa0@z> (raw)
In-Reply-To: <CAAA5faHubPyT8D+QYB_M+qyCo-rRzPDO3fSH1HtSXCfCTj40HA@mail.gmail.com>
On 07/15/2015 08:56 PM, Reinoud Koornstra wrote:
> Thanks for your answer.
> Is this patch going in upstream
> Thanks,
>
> Reinoud
>
It's already upstream just not in 3.10. A more recent kernel should
compile fine with your toolchain.
--
markos
next prev parent reply other threads:[~2015-07-16 8:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-14 18:04 compile failure linux 3.10 with gcc 4.9.3 for mips Reinoud Koornstra
2015-07-15 8:03 ` Markos Chandras
2015-07-15 8:03 ` Markos Chandras
2015-07-15 19:56 ` Reinoud Koornstra
2015-07-16 8:42 ` Markos Chandras [this message]
2015-07-16 8:42 ` Markos Chandras
-- strict thread matches above, loose matches on Subject: below --
2015-07-13 23:52 Reinoud Koornstra
2015-07-15 4:38 ` Khem Raj
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=55A76E71.8090909@imgtec.com \
--to=markos.chandras@imgtec.com \
--cc=linux-mips@linux-mips.org \
--cc=reinoudkoornstra@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 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.