public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	Andy Lutomirski <luto@amacapital.net>,
	Andrew Morton <akpm@linux-foundation.org>,
	James Hogan <james.hogan@imgtec.com>,
	linux-metag@vger.kernel.org
Subject: Re: linux-next: Tree for Dec 16
Date: Mon, 15 Dec 2014 22:35:49 -0800	[thread overview]
Message-ID: <20141216063549.GA1060@roeck-us.net> (raw)
In-Reply-To: <20141216154622.7c2ded16@canb.auug.org.au>

On Tue, Dec 16, 2014 at 03:46:22PM +1100, Stephen Rothwell wrote:
> Hi all,
> 
> Please do not add any code destined for v3.20 to your linux-next included
> trees/branches until after v3.19-rc1 is released.
> 
> Changes since 20141215:
> 
> The infiniband tree gained a conflict against Linus' tree and a build
> failure so I used the version from next-20141215.
> 
> The userns tree gained a conflict against the vfs tree.
> 
> The clk tree gained a build failure so I used the version from
> next-20141215.
> 
> Non-merge commits (relative to Linus' tree): 3588
>  2582 files changed, 123494 insertions(+), 135748 deletions(-)
> 

My metag buildbot test fails with this kernel.

bisect result:

a82be12232dcccf6b914cec7458e96ee79fae0e3 is the first bad commit
commit a82be12232dcccf6b914cec7458e96ee79fae0e3
Author: Andy Lutomirski <luto@amacapital.net>
Date:   Tue Dec 16 13:26:43 2014 +1100

    all arches, signal: move restart_block to struct task_struct

bisect log:

# bad: [a0eda581bf3fdc7be6bdf4cb18ce087675699336] Add linux-next specific files for 20141216
# good: [b2776bf7149bddd1f4161f14f79520f17fc1d71d] Linux 3.18
git bisect start 'HEAD' 'v3.18'
# good: [27afc5dbda52ee3dbcd0bda7375c917c6936b470] Merge branch 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/s390/linux
git bisect good 27afc5dbda52ee3dbcd0bda7375c917c6936b470
# good: [a5e6d5b3bb7124309ce581e9e050e029ab037609] Merge remote-tracking branch 'l2-mtd/master'
git bisect good a5e6d5b3bb7124309ce581e9e050e029ab037609
# good: [93cc1d514a7e8bc4e00ce913ddccb34ee8a2a001] Merge remote-tracking branch 'ipmi/for-next'
git bisect good 93cc1d514a7e8bc4e00ce913ddccb34ee8a2a001
# good: [865cde938ee6ab758fd47d1a36150aee20371b85] staging: unisys: virtpci: Fix CamelCase in delete_vbus_device()
git bisect good 865cde938ee6ab758fd47d1a36150aee20371b85
# good: [594e400a2c3a64d7c3ba8ad7b0196c887a354100] staging: comedi: das6402: add basic (*do_cmdtest) for AI async commands
git bisect good 594e400a2c3a64d7c3ba8ad7b0196c887a354100
# good: [4e8bb35b814a1377dcaf48b98d4ab29176528cdc] Merge remote-tracking branch 'target-updates/for-next'
git bisect good 4e8bb35b814a1377dcaf48b98d4ab29176528cdc
# good: [e03f3bb62ca8a1124bc408046c50aed7629b24cc] next-20141215/clk
git bisect good e03f3bb62ca8a1124bc408046c50aed7629b24cc
# bad: [a82be12232dcccf6b914cec7458e96ee79fae0e3] all arches, signal: move restart_block to struct task_struct
git bisect bad a82be12232dcccf6b914cec7458e96ee79fae0e3
# good: [4425fdc4c01ab7699072a417741a008b0dca576b] ocfs2: do not fallback to buffer I/O write if appending
git bisect good 4425fdc4c01ab7699072a417741a008b0dca576b
# good: [98b090c1d15d1c94f01f071b283ce44be8644220] mm: define MADV_FREE for some arches
git bisect good 98b090c1d15d1c94f01f071b283ce44be8644220
# good: [ca402e9bfbbac21d3d7541c33adb60f7ebcc480e] arm: add pmd_mkclean for THP
git bisect good ca402e9bfbbac21d3d7541c33adb60f7ebcc480e
# good: [60eeb1279b50c205f045d2b7c76c906a2d2fb751] mm: Fix comment typo "CONFIG_TRANSPARNTE_HUGE"
git bisect good 60eeb1279b50c205f045d2b7c76c906a2d2fb751
# good: [1134212f12cb9e5b3c24b7be5cfa304486f2f96b] do_shared_fault(): check that mmap_sem is held
git bisect good 1134212f12cb9e5b3c24b7be5cfa304486f2f96b
# first bad commit: [a82be12232dcccf6b914cec7458e96ee79fae0e3] all arches, signal: move restart_block to struct task_struct

--

Guenter

  reply	other threads:[~2014-12-16  6:36 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-16  4:46 linux-next: Tree for Dec 16 Stephen Rothwell
2014-12-16  6:35 ` Guenter Roeck [this message]
2014-12-16  6:44   ` Andrew Morton
2014-12-16  6:55     ` Guenter Roeck
2014-12-16  9:42       ` James Hogan
2014-12-16 10:45         ` James Hogan
2014-12-16 23:57           ` Stephen Rothwell
2014-12-17  0:08             ` Andrew Morton
2014-12-17  0:23               ` Stephen Rothwell
  -- strict thread matches above, loose matches on Subject: below --
2025-12-16  1:47 Stephen Rothwell
2024-12-16  6:25 Stephen Rothwell
2022-12-16  1:46 Stephen Rothwell
2020-12-16  9:40 Stephen Rothwell
2019-12-16  5:22 Stephen Rothwell
2016-12-16  3:49 Stephen Rothwell
2015-12-16  5:43 Stephen Rothwell
2013-12-16  5:59 Stephen Rothwell
2011-12-16  6:00 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=20141216063549.GA1060@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=akpm@linux-foundation.org \
    --cc=james.hogan@imgtec.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-metag@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=luto@amacapital.net \
    --cc=sfr@canb.auug.org.au \
    /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