linux-kernel.vger.kernel.org archive mirror
 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,
	Helge Deller <deller@gmx.de>, Ingo Molnar <mingo@kernel.org>
Subject: Re: linux-next: Tree for Sep 19
Date: Fri, 19 Sep 2014 12:15:14 -0700	[thread overview]
Message-ID: <20140919191514.GA5358@roeck-us.net> (raw)
In-Reply-To: <20140919165817.225eb8b8@canb.auug.org.au>

On Fri, Sep 19, 2014 at 04:58:17PM +1000, Stephen Rothwell wrote:
> Hi all,
> 
> Changes since 20140917:
> 
> The fsl tree still had its build failure so I used the version from
> next-20140917.
> 
> The v4l-dvb tree lost its build failure.
> 
> The security tree gained a conflict against the file-locks tree.
> 
> Non-merge commits (relative to Linus' tree): 6014
>  5488 files changed, 217522 insertions(+), 129375 deletions(-)
> 
> ----------------------------------------------------------------------------
> 

parisc:defconfig, parisc:generic-32bit_defconfig:

--------------
Error log:
arch/parisc/kernel/ptrace.c: In function 'do_syscall_trace_enter':
arch/parisc/kernel/ptrace.c:274:2: error: implicit declaration of function
'secure_computing' [-Werror=implicit-function-declaration]
cc1: some warnings being treated as errors
make[1]: *** [arch/parisc/kernel/ptrace.o] Error 1

Bisect points to commit 273299fb6380 ('Merge branch 'x86/seccomp') which
obviously doesn't help much. Suspected culprit is c90f06943e05 ('parisc: Wire up
seccomp, getrandom and memfd_create syscalls') which seems to be missing an
include file.

Bisect log:

# bad: [6a10bca9b608df445baa23c3bfafc510d93d425b] Add linux-next specific files for 20140919
# good: [9e82bf014195d6f0054982c463575cdce24292be] Linux 3.17-rc5
git bisect start 'HEAD' 'v3.17-rc5'
# good: [fde058e2322b9098251d7cf798cac4327a29c004] Merge remote-tracking branch 'drm/drm-next'
git bisect good fde058e2322b9098251d7cf798cac4327a29c004
# bad: [8a258c1a0f82f4d152a3b06966a4d28dac2c8bcb] Merge remote-tracking branch 'usb-serial/usb-next'
git bisect bad 8a258c1a0f82f4d152a3b06966a4d28dac2c8bcb
# good: [5a571cebb73888024182de09063db35341e61beb] Merge remote-tracking branch 'spi/for-next'
git bisect good 5a571cebb73888024182de09063db35341e61beb
# bad: [249a58bd0f355bc12549d00296684103326ac38f] Merge remote-tracking branch 'rcu/rcu/next'
git bisect bad 249a58bd0f355bc12549d00296684103326ac38f
# good: [50a919fbd52123bd30c8f788a28343bfb159f855] Merge branch 'perf/core'
git bisect good 50a919fbd52123bd30c8f788a28343bfb159f855
# bad: [1187356a4b781969c160a9c21c164f738747fc66] Merge remote-tracking branch 'tip/auto-latest'
git bisect bad 1187356a4b781969c160a9c21c164f738747fc66
# good: [20ef49c29af54140f51657961a37d6a59c80b479] Merge branch 'x86/cleanups'
git bisect good 20ef49c29af54140f51657961a37d6a59c80b479
# good: [63feeed278579155f0dff01b13167034cde470b2] Merge branch 'x86/mm'
git bisect good 63feeed278579155f0dff01b13167034cde470b2
# bad: [273299fb6380d08414b2710d007252f23b7dcc8f] Merge branch 'x86/seccomp'
git bisect bad 273299fb6380d08414b2710d007252f23b7dcc8f
# good: [e0ffbaabc46db508b8717f023c0ce03b980eefac] x86: Split syscall_trace_enter into two phases
git bisect good e0ffbaabc46db508b8717f023c0ce03b980eefac
# good: [2e151c70dfb0075ff83bec305c52a9da1ba49089] x86: HPET force enable for e6xx based systems
git bisect good 2e151c70dfb0075ff83bec305c52a9da1ba49089
# good: [1dcf74f6edfc3a9acd84d83d8865dd9e2a3b1d1e] x86_64, entry: Use split-phase syscall_trace_enter for 64-bit syscalls
git bisect good 1dcf74f6edfc3a9acd84d83d8865dd9e2a3b1d1e
# good: [aa22686f4231a72583d03882e841eba2de4b1ee6] Merge branch 'x86/platform'
git bisect good aa22686f4231a72583d03882e841eba2de4b1ee6
# first bad commit: [273299fb6380d08414b2710d007252f23b7dcc8f] Merge branch 'x86/seccomp'

  parent reply	other threads:[~2014-09-19 19:15 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-19  6:58 linux-next: Tree for Sep 19 Stephen Rothwell
2014-09-19 19:04 ` Guenter Roeck
2014-09-19 19:15 ` Guenter Roeck [this message]
2014-09-20 19:36   ` Helge Deller
2014-09-20 21:01     ` Guenter Roeck
2014-09-21 19:43       ` Helge Deller
2014-09-19 19:42 ` Guenter Roeck
2014-09-19 20:06 ` Guenter Roeck
2014-09-22 14:40   ` Christoph Hellwig
2014-09-19 20:24 ` Guenter Roeck
2014-09-22 14:35   ` Christoph Hellwig
2014-09-19 21:14 ` Guenter Roeck
2014-09-19 21:42   ` Anish Bhatt
2014-09-20  0:18     ` Guenter Roeck
2014-09-19 22:21   ` Randy Dunlap
2014-09-19 22:28     ` Anish Bhatt
2014-09-19 22:35       ` Randy Dunlap
2014-09-20  0:15     ` Guenter Roeck
2014-09-20  1:09       ` Randy Dunlap
2014-09-20  1:43         ` Anish Bhatt
2014-09-20  2:08           ` David Miller
2014-09-20  2:40             ` Guenter Roeck
  -- strict thread matches above, loose matches on Subject: below --
2025-09-19 15:05 Mark Brown
2024-09-19  5:46 Stephen Rothwell
2023-09-19  6:37 Stephen Rothwell
2022-09-19  9:47 Stephen Rothwell
2019-09-19 16:06 Mark Brown
2018-09-19  6:16 Stephen Rothwell
2017-09-19  4:15 Stephen Rothwell
2016-09-19  7:02 Stephen Rothwell
2013-09-19  3:59 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=20140919191514.GA5358@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=deller@gmx.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mingo@kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).