From: Bob Tracy <rct@gherkin.frus.com>
To: "Maciej W. Rozycki" <macro@linux-mips.org>
Cc: linux-kernel@vger.kernel.org, debian-alpha@lists.debian.org,
mcree@orcon.net.nz, jay.estabrook@gmail.com, mattst88@gmail.com
Subject: Re: [BUG] machine check Oops on Alpha
Date: Mon, 18 Apr 2016 21:52:43 -0500 [thread overview]
Message-ID: <20160419025243.GA32734@gherkin.frus.com> (raw)
In-Reply-To: <alpine.LFD.2.20.1604181436170.28036@eddie.linux-mips.org>
On Mon, Apr 18, 2016 at 02:47:40PM +0100, Maciej W. Rozycki wrote:
> On Mon, 18 Apr 2016, Bob Tracy wrote:
>
> > Build delayed slightly. Ran into "fs/binfmt_em86.o" build failure
> > patched by Daniel Wagner back in February (incompatible-pointer-types
> > warning treated as error by compiler). Is Daniel's patch queued for
> > incorporation into the main kernel source tree?
>
> No idea. I've had a peek at the patch though and it groups unrelated
> changes together and also mixes obvious semantics fixes (missing `const'
> qualifier) with semantic changes (`i_arg' removal) which may need further
> consideration. I think splitting that proposal into ~3 self-contained
> changes may rise the likelihood of at least the critical parts being
> accepted.
4.6.0-rc4 build complete, including suggested (by Alan Young) "Verbose
Machine Checks" option set to level 2 by default. System rebooted, and
now we wait... Thanks for everyone's continued patience.
--Bob
next prev parent reply other threads:[~2016-04-19 2:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-17 21:05 [BUG] machine check Oops on Alpha Bob Tracy
2016-04-18 1:32 ` Maciej W. Rozycki
2016-04-18 3:58 ` Bob Tracy
2016-04-18 12:31 ` Bob Tracy
2016-04-18 13:47 ` Maciej W. Rozycki
2016-04-19 2:52 ` Bob Tracy [this message]
2016-04-19 23:56 ` Bob Tracy
2016-04-20 0:46 ` Maciej W. Rozycki
2016-04-20 3:57 ` Bob Tracy
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=20160419025243.GA32734@gherkin.frus.com \
--to=rct@gherkin.frus.com \
--cc=debian-alpha@lists.debian.org \
--cc=jay.estabrook@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=macro@linux-mips.org \
--cc=mattst88@gmail.com \
--cc=mcree@orcon.net.nz \
/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).