From: James Hogan <james.hogan@imgtec.com>
To: Ingo Molnar <mingo@kernel.org>
Cc: Guenter Roeck <linux@roeck-us.net>,
Ralf Baechle <ralf@linux-mips.org>,
Herbert Xu <herbert@gondor.apana.org.au>,
<linux-mips@linux-mips.org>, <linux-kernel@vger.kernel.org>,
<linux-crypto@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH v3] MIPS: Fix build breakage caused by header file changes
Date: Tue, 7 Mar 2017 09:38:50 +0000 [thread overview]
Message-ID: <20170307093850.GD996@jhogan-linux.le.imgtec.org> (raw)
In-Reply-To: <20170307073805.GB15693@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 566 bytes --]
Hi Ingo,
On Tue, Mar 07, 2017 at 08:38:05AM +0100, Ingo Molnar wrote:
> Just a quick question: is your MIPS build fix going to be merged and sent to
> Linus? I can apply it too, and send it to Linus later today, together with a few
> other sched.h header related build fixes.
One for Ralf...
> Assuming it's all properly tested - my limited MIPS defconfig builds worked fine -
> but MIPS has a lot of build variations.
If you have a branch with other generic fixes I'm happy to push it to
our MIPS buildbot too to double check.
Cheers
James
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: James Hogan <james.hogan@imgtec.com>
To: Ingo Molnar <mingo@kernel.org>
Cc: Guenter Roeck <linux@roeck-us.net>,
Ralf Baechle <ralf@linux-mips.org>,
Herbert Xu <herbert@gondor.apana.org.au>,
linux-mips@linux-mips.org, linux-kernel@vger.kernel.org,
linux-crypto@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH v3] MIPS: Fix build breakage caused by header file changes
Date: Tue, 7 Mar 2017 09:38:50 +0000 [thread overview]
Message-ID: <20170307093850.GD996@jhogan-linux.le.imgtec.org> (raw)
Message-ID: <20170307093850.epaXk_sKY_-quEv-WRP2SEae6C1ht6TQB8kvx_a9npM@z> (raw)
In-Reply-To: <20170307073805.GB15693@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 566 bytes --]
Hi Ingo,
On Tue, Mar 07, 2017 at 08:38:05AM +0100, Ingo Molnar wrote:
> Just a quick question: is your MIPS build fix going to be merged and sent to
> Linus? I can apply it too, and send it to Linus later today, together with a few
> other sched.h header related build fixes.
One for Ralf...
> Assuming it's all properly tested - my limited MIPS defconfig builds worked fine -
> but MIPS has a lot of build variations.
If you have a branch with other generic fixes I'm happy to push it to
our MIPS buildbot too to double check.
Cheers
James
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next prev parent reply other threads:[~2017-03-07 9:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-06 19:13 [PATCH v3] MIPS: Fix build breakage caused by header file changes Guenter Roeck
2017-03-06 23:20 ` James Hogan
2017-03-06 23:20 ` James Hogan
2017-03-07 3:30 ` Guenter Roeck
2017-03-07 9:33 ` James Hogan
2017-03-07 9:33 ` James Hogan
2017-03-07 10:31 ` James Hogan
2017-03-07 10:31 ` James Hogan
2017-03-07 7:38 ` Ingo Molnar
2017-03-07 9:38 ` James Hogan [this message]
2017-03-07 9:38 ` James Hogan
2017-03-07 10:34 ` Ingo Molnar
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=20170307093850.GD996@jhogan-linux.le.imgtec.org \
--to=james.hogan@imgtec.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=linux@roeck-us.net \
--cc=mingo@kernel.org \
--cc=ralf@linux-mips.org \
--cc=torvalds@linux-foundation.org \
/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