From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
airlied@linux.ie, dri-devel@lists.freedesktop.org
Cc: "linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
zhi.a.wang@intel.com, zhenyuw@linux.intel.com
Subject: Re: linux-next: Tree for Oct 25
Date: Tue, 25 Oct 2016 21:09:33 -0400 [thread overview]
Message-ID: <CAP=VYLqdh2E17pZmEwQWS66Y9jdx-3SHsZkt5e4nitpg1N-A_g@mail.gmail.com> (raw)
In-Reply-To: <20161025143134.7ab67718@canb.auug.org.au>
On Mon, Oct 24, 2016 at 11:31 PM, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> Hi all,
>
> There will probably be no linux-next releases next week while I attend
> the Kernel Summit.
>
> Changes since 20161024:
>
> The pm tree gained a conflict against the imx-mxs tree.
>
> The mali-dp tree gained a conflict against the drm-misc tree.
>
> The sunxi tree gained a build failure so I used the version from
> next-20161024.
>
> The akpm-current tree still had its build failures for which I applied
> 2 patches.
>
> Non-merge commits (relative to Linus' tree): 2174
> 2622 files changed, 187829 insertions(+), 38953 deletions(-)
The i386 allmodconfig fails with bad 32/64 math for about the last 5 days.
ERROR: "__umoddi3" [drivers/gpu/drm/i915/i915.ko] undefined!
http://kisskb.ellerman.id.au/kisskb/buildresult/12840554/
git bisect says:
first bad commit: [4d60c5fd3f8751ea751d6dc6cfe0c1620420ccf8]
drm/i915/gvt: vGPU PCI configuration space virtualization
Authors/maintainers added to Cc/To list. Guessing folks weren't
aware of the regression.
Thanks,
Paul.
next prev parent reply other threads:[~2016-10-26 1:10 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-25 3:31 linux-next: Tree for Oct 25 Stephen Rothwell
2016-10-26 1:09 ` Paul Gortmaker [this message]
2016-10-27 6:21 ` Daniel Vetter
-- strict thread matches above, loose matches on Subject: below --
2023-10-25 5:37 Stephen Rothwell
2022-10-25 4:20 Stephen Rothwell
2021-10-25 9:49 Stephen Rothwell
2021-10-25 22:11 ` Dmitry Osipenko
2021-10-26 1:28 ` Ming Lei
2021-10-26 8:40 ` Dmitry Osipenko
2021-10-27 11:42 ` Stephen Rothwell
2021-10-27 12:54 ` Greg Kroah-Hartman
2021-10-28 1:51 ` Xianting Tian
2021-10-28 4:51 ` Stephen Rothwell
2021-10-28 7:59 ` Xianting Tian
2021-10-28 12:48 ` Stephen Rothwell
2021-10-28 12:54 ` Xianting Tian
2019-10-25 5:45 Stephen Rothwell
2013-10-25 15:03 Thierry Reding
2013-10-25 21:01 ` Guenter Roeck
2013-10-25 22:31 ` Randy Dunlap
2013-10-26 16:59 ` Mark Brown
2013-10-28 8:01 ` Thierry Reding
2013-10-28 16:53 ` Mark Brown
2012-10-25 4:01 Stephen Rothwell
2011-10-25 9:36 Stephen Rothwell
2011-10-25 9:43 ` Stephen Rothwell
2011-10-25 10:42 ` 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='CAP=VYLqdh2E17pZmEwQWS66Y9jdx-3SHsZkt5e4nitpg1N-A_g@mail.gmail.com' \
--to=paul.gortmaker@windriver.com \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=zhenyuw@linux.intel.com \
--cc=zhi.a.wang@intel.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).