From: viro@ZenIV.linux.org.uk (Al Viro)
To: linux-arm-kernel@lists.infradead.org
Subject: v4.10-rc1 - build failure arm64?
Date: Mon, 26 Dec 2016 18:49:51 +0000 [thread overview]
Message-ID: <20161226184951.GS1555@ZenIV.linux.org.uk> (raw)
In-Reply-To: <e47e230c-4e76-a7b7-a408-ada809a3b1b8@ti.com>
On Mon, Dec 26, 2016 at 12:46:58PM -0600, Nishanth Menon wrote:
> A bit of bisect later, looks like reverting the following commit allows the
> build to proceed. -> note: there is no fail on multi_v7_defconfig or
> omap2plus_defconfig even without the revert.
See git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git#arm64-fix
WARNING: multiple messages have this Message-ID (diff)
From: Al Viro <viro@ZenIV.linux.org.uk>
To: Nishanth Menon <nm@ti.com>
Cc: linux-arm-kernel@lists.infradead.org,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: v4.10-rc1 - build failure arm64?
Date: Mon, 26 Dec 2016 18:49:51 +0000 [thread overview]
Message-ID: <20161226184951.GS1555@ZenIV.linux.org.uk> (raw)
In-Reply-To: <e47e230c-4e76-a7b7-a408-ada809a3b1b8@ti.com>
On Mon, Dec 26, 2016 at 12:46:58PM -0600, Nishanth Menon wrote:
> A bit of bisect later, looks like reverting the following commit allows the
> build to proceed. -> note: there is no fail on multi_v7_defconfig or
> omap2plus_defconfig even without the revert.
See git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git#arm64-fix
next prev parent reply other threads:[~2016-12-26 18:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-26 18:30 v4.10-rc1 - build failure arm64? Nishanth Menon
2016-12-26 18:46 ` Nishanth Menon
2016-12-26 18:46 ` Nishanth Menon
2016-12-26 18:49 ` Al Viro [this message]
2016-12-26 18:49 ` Al Viro
2016-12-26 18:56 ` Nishanth Menon
2016-12-26 18:56 ` Nishanth Menon
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=20161226184951.GS1555@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=linux-arm-kernel@lists.infradead.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 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.