Hi Sedat,
On Sat, 27 Mar 2021 12:50:55 +0100 Sedat Dilek wrote:
>
> I wonder why Stephen's fixup-patch was not carried in recent
> Linux-next releases.
It is part of the tip tree merge commit. So it is not an explicit
commit on its own, but the needed change is there.
> Wild speculation - no r
On Fri, Mar 26, 2021 at 2:11 PM Borislav Petkov wrote:
>
> On Fri, Mar 26, 2021 at 09:57:43AM +0100, Sedat Dilek wrote:
> > The commit b90829704780 "bpf: Use NOP_ATOMIC5 instead of
> > emit_nops(&prog, 5) for BPF_TRAMP_F_CALL_ORIG" is now in Linus Git
> > (see [1]).
> >
> > Where will Stephen's fi
On Fri, Mar 26, 2021 at 09:57:43AM +0100, Sedat Dilek wrote:
> The commit b90829704780 "bpf: Use NOP_ATOMIC5 instead of
> emit_nops(&prog, 5) for BPF_TRAMP_F_CALL_ORIG" is now in Linus Git
> (see [1]).
>
> Where will Stephen's fixup-patch be carried?
> Linux-next?
> net-next?
> ?
I guess we'll re
On Mon, Mar 22, 2021 at 10:02 AM Borislav Petkov wrote:
>
> On Mon, Mar 22, 2021 at 02:37:14PM +1100, Stephen Rothwell wrote:
> > Hi all,
> >
> > After merging the tip tree, today's linux-next build (x86_64 allmodconfig)
> > failed like this:
> >
> > arch/x86/net/bpf_jit_comp.c: In function 'arch_
On Mon, Mar 22, 2021 at 4:39 AM Stephen Rothwell wrote:
>
> Hi all,
>
> After merging the tip tree, today's linux-next build (x86_64 allmodconfig)
> failed like this:
>
> arch/x86/net/bpf_jit_comp.c: In function 'arch_prepare_bpf_trampoline':
> arch/x86/net/bpf_jit_comp.c:2015:16: error: 'ideal_no
On Mon, Mar 22, 2021 at 02:37:14PM +1100, Stephen Rothwell wrote:
> Hi all,
>
> After merging the tip tree, today's linux-next build (x86_64 allmodconfig)
> failed like this:
>
> arch/x86/net/bpf_jit_comp.c: In function 'arch_prepare_bpf_trampoline':
> arch/x86/net/bpf_jit_comp.c:2015:16: error:
Hi Ingo,
On Wed, 17 Mar 2021 21:04:08 +0100 Ingo Molnar wrote:
>
> * Borislav Petkov wrote:
>
> > On Thu, Mar 18, 2021 at 05:49:21AM +1100, Stephen Rothwell wrote:
> > > That fixes the powerpc build for me, thanks.
> >
> > Thx, adding your Tested-by and pushing out.
>
> I've pushed this
* Borislav Petkov wrote:
> On Thu, Mar 18, 2021 at 05:49:21AM +1100, Stephen Rothwell wrote:
> > That fixes the powerpc build for me, thanks.
>
> Thx, adding your Tested-by and pushing out.
I've pushed this out into tip:auto-latest as well, so that tomorrow's
-next should pick this up automa
On Thu, Mar 18, 2021 at 05:49:21AM +1100, Stephen Rothwell wrote:
> That fixes the powerpc build for me, thanks.
Thx, adding your Tested-by and pushing out.
--
Regards/Gruss,
Boris.
SUSE Software Solutions Germany GmbH, GF: Felix Imendörffer, HRB 36809, AG
Nürnberg
Hi Borislav,
On Wed, 17 Mar 2021 19:02:36 +0100 Borislav Petkov wrote:
>
> On Wed, Mar 17, 2021 at 09:22:15AM -0700, Ian Rogers wrote:
> > The path also needs fixing. With the following
> > I was able to build for arm64 and powerpc.
>
> Thanks, I've updated and added your Tested-by. I'll give
On Wed, Mar 17, 2021 at 09:22:15AM -0700, Ian Rogers wrote:
> The path also needs fixing. With the following
> I was able to build for arm64 and powerpc.
Thanks, I've updated and added your Tested-by. I'll give sfr a chance to
test and queue it tomorrow.
---
>From d242b2639a23ed03d9aed94cf05b99a
On Wed, Mar 17, 2021 at 3:54 AM Borislav Petkov wrote:
>
> + Ian.
>
> On Wed, Mar 17, 2021 at 03:08:58PM +1100, Stephen Rothwell wrote:
> > Hi all,
> >
> > After merging the tip tree, today's linux-next build (native perf)
> > failed like this:
> >
> > In file included from util/intel-pt-decoder/i
+ Ian.
On Wed, Mar 17, 2021 at 03:08:58PM +1100, Stephen Rothwell wrote:
> Hi all,
>
> After merging the tip tree, today's linux-next build (native perf)
> failed like this:
>
> In file included from util/intel-pt-decoder/intel-pt-insn-decoder.c:15:
> util/intel-pt-decoder/../../../arch/x86/lib/
Hi Peter,
On Wed, 3 Mar 2021 10:44:32 +0100 Peter Zijlstra wrote:
>
> Damn, sorry about that. I've rebased tip/sched/core and all should be
> well now.
Excellent, thanks.
--
Cheers,
Stephen Rothwell
pgpxZzQ5s2EcR.pgp
Description: OpenPGP digital signature
On Wed, Mar 03, 2021 at 10:38:42AM +1100, Stephen Rothwell wrote:
> Hi all,
>
> After merging the tip tree, today's linux-next build (x86_64 allmodconfig)
> failed like this:
>
> In file included from drivers/usb/usbip/usbip_common.c:18:
> drivers/usb/usbip/usbip_common.h: In function 'usbip_kcov
On Thu, Jan 14, 2021 at 03:11:45PM +1100, Stephen Rothwell wrote:
> Hi all,
>
> After merging the tip tree, today's linux-next build (x86_64 allnoconfig)
> failed like this:
>
> arch/x86/kernel/cpu/amd.c: In function 'bsp_init_amd':
> arch/x86/kernel/cpu/amd.c:545:3: error: '__max_die_per_package
* Stephen Rothwell wrote:
> Hi all,
>
> After merging the tip tree, today's linux-next build (x86_64 allmodconfig)
> failed like this:
>
> kernel/smp.c: In function 'csd_lock_wait_getcpu':
> kernel/smp.c:133:13: error: 'call_single_data_t' {aka 'struct
> __call_single_data'} has no member na
On Fri, Oct 09, 2020 at 03:28:46PM +1100, Stephen Rothwell wrote:
> Hi all,
>
> After merging the tip tree, today's linux-next build (perf) failed
> like this:
>
> In file included from tools/include/linux/build_bug.h:5,
> from tools/include/linux/kernel.h:8,
> f
On Tue, Sep 08, 2020 at 07:12:23PM +1000, Stephen Rothwell wrote:
> Hi all,
>
> After merging the tip tree, today's linux-next build (powerpc
> allyesconfig) failed like this:
>
> ERROR: modpost: too long symbol
> ".__tracepoint_iter_pnfs_mds_fallback_pg_get_mirror_count"
> [fs/nfs/flexfilelayo
Hi Ingo,
On Thu, 3 Sep 2020 05:51:08 +0200 Ingo Molnar wrote:
>
> I've merged the old commit by mistake - it's removed now.
Ah, OK, thanks.
--
Cheers,
Stephen Rothwell
pgpqbzuw8G3mY.pgp
Description: OpenPGP digital signature
* Stephen Rothwell wrote:
> Hi all,
>
> After merging the tip tree, today's linux-next build (powerpc
> ppc64_defconfig) failed like this:
>
>
> Caused by commit
>
> f670269a42bf ("x86: Fix early boot crash on gcc-10, next try")
>
> interacting with commit
>
> a9a3ed1eff36 ("x86: Fix
Hi Ingo,
On Fri, 31 Jul 2020 11:57:35 +0200 Ingo Molnar wrote:
>
> I've merged Linus's latest into tip:locking/core, keeping the simpler
> solution of a6342915881a and reducing the dependency hell.
>
> Will push it all out hopefully later today (unrelated changes need
> more testing), from tha
* Stephen Rothwell wrote:
> Hi all,
>
> After merging the tip tree, today's linux-next build (arm
> multi_v7_defconfig) failed like this:
>
> In file included from include/asm-generic/getorder.h:8,
> from arch/arm/include/asm/page.h:166,
> from arch/arm/inclu
Hi all,
On Tue, 14 Jul 2020 13:50:12 +1000 Stephen Rothwell
wrote:
>
> On Tue, 7 Jul 2020 12:33:01 +1000 Stephen Rothwell
> wrote:
> >
> > On Tue, 30 Jun 2020 12:54:59 +1000 Stephen Rothwell
> > wrote:
> > >
> > > On Mon, 22 Jun 2020 11:37:00 +1000 Stephen Rothwell
> > > wrote:
> > >
Hi all,
On Tue, 7 Jul 2020 12:33:01 +1000 Stephen Rothwell
wrote:
>
> On Tue, 30 Jun 2020 12:54:59 +1000 Stephen Rothwell
> wrote:
> >
> > On Mon, 22 Jun 2020 11:37:00 +1000 Stephen Rothwell
> > wrote:
> > >
> > > After merging the tip tree, today's linux-next build (x86_64 allmodconfig)
>
Hi all,
On Tue, 30 Jun 2020 12:54:59 +1000 Stephen Rothwell
wrote:
>
> On Mon, 22 Jun 2020 11:37:00 +1000 Stephen Rothwell
> wrote:
> >
> > After merging the tip tree, today's linux-next build (x86_64 allmodconfig)
> > failed like this:
> >
> > ERROR: modpost: "sched_setscheduler"
> > [kerne
Hi all,
On Mon, 22 Jun 2020 11:37:00 +1000 Stephen Rothwell
wrote:
>
> After merging the tip tree, today's linux-next build (x86_64 allmodconfig)
> failed like this:
>
> ERROR: modpost: "sched_setscheduler" [kernel/trace/ring_buffer_benchmark.ko]
> undefined!
>
> Caused by commit
>
> 616d9
Hi Borislav,
On Sun, 21 Jun 2020 12:53:50 +0200 Borislav Petkov wrote:
>
> + acme for an FYI.
>
> On Sun, Jun 21, 2020 at 04:33:23PM +1000, Stephen Rothwell wrote:
> > Hi all,
> >
> > After merging the tip tree, today's linux-next build (perf) failed
> > like this:
> >
> > In file included fro
+ acme for an FYI.
On Sun, Jun 21, 2020 at 04:33:23PM +1000, Stephen Rothwell wrote:
> Hi all,
>
> After merging the tip tree, today's linux-next build (perf) failed
> like this:
>
> In file included from trace/beauty/tracepoints/x86_msr.c:10:
> perf/trace/beauty/generated/x86_arch_MSRs_array.c:
On Mon, May 25, 2020 at 10:20:29AM +0200, Marco Elver wrote:
> On Mon, 25 May 2020 at 02:37, Paul E. McKenney wrote:
> >
> > On Sat, May 23, 2020 at 02:23:45PM -0700, Paul E. McKenney wrote:
> > > On Sat, May 23, 2020 at 09:05:24PM +0200, Thomas Gleixner wrote:
> > > > "Paul E. McKenney" writes:
On Mon, 25 May 2020 at 02:37, Paul E. McKenney wrote:
>
> On Sat, May 23, 2020 at 02:23:45PM -0700, Paul E. McKenney wrote:
> > On Sat, May 23, 2020 at 09:05:24PM +0200, Thomas Gleixner wrote:
> > > "Paul E. McKenney" writes:
> > > > On Sat, May 23, 2020 at 11:54:26AM +0200, Thomas Gleixner wrote
On Sat, May 23, 2020 at 02:23:45PM -0700, Paul E. McKenney wrote:
> On Sat, May 23, 2020 at 09:05:24PM +0200, Thomas Gleixner wrote:
> > "Paul E. McKenney" writes:
> > > On Sat, May 23, 2020 at 11:54:26AM +0200, Thomas Gleixner wrote:
> > >> core/rcu is the one which diverged and caused the merge
On Sat, May 23, 2020 at 09:05:24PM +0200, Thomas Gleixner wrote:
> "Paul E. McKenney" writes:
> > On Sat, May 23, 2020 at 11:54:26AM +0200, Thomas Gleixner wrote:
> >> core/rcu is the one which diverged and caused the merge conflict with
> >> PPC to happen twice. So Paul needs to remove the stale
"Paul E. McKenney" writes:
> On Sat, May 23, 2020 at 11:54:26AM +0200, Thomas Gleixner wrote:
>> core/rcu is the one which diverged and caused the merge conflict with
>> PPC to happen twice. So Paul needs to remove the stale core/rcu bits and
>> rebase on the current version (which is not going to
On Sat, May 23, 2020 at 11:54:26AM +0200, Thomas Gleixner wrote:
> Borislav Petkov writes:
>
> > On Fri, May 22, 2020 at 05:12:23PM -0700, Paul E. McKenney wrote:
> >> Marco, Thomas, is there any better setup I can provide Stephen? Or
> >> is the next-20200519 -rcu tree the best we have right no
Borislav Petkov writes:
> On Fri, May 22, 2020 at 05:12:23PM -0700, Paul E. McKenney wrote:
>> Marco, Thomas, is there any better setup I can provide Stephen? Or
>> is the next-20200519 -rcu tree the best we have right now?
>
> I've queued the fixes yesterday into tip:locking/kcsan and tglx said
On Fri, May 22, 2020 at 05:12:23PM -0700, Paul E. McKenney wrote:
> Marco, Thomas, is there any better setup I can provide Stephen? Or
> is the next-20200519 -rcu tree the best we have right now?
I've queued the fixes yesterday into tip:locking/kcsan and tglx said
something about you having to re
On Fri, May 22, 2020 at 05:49:44PM +1000, Stephen Rothwell wrote:
> Hi all,
>
> On Fri, 22 May 2020 17:17:08 +1000 Stephen Rothwell
> wrote:
> >
> > On Thu, 21 May 2020 18:35:22 +0100 Will Deacon wrote:
> > >
> > > [+Marco and Boris]
> > >
> > > On Fri, May 22, 2020 at 03:31:19AM +1000, Stephe
Hi all,
On Fri, 22 May 2020 17:17:08 +1000 Stephen Rothwell
wrote:
>
> On Thu, 21 May 2020 18:35:22 +0100 Will Deacon wrote:
> >
> > [+Marco and Boris]
> >
> > On Fri, May 22, 2020 at 03:31:19AM +1000, Stephen Rothwell wrote:
> > > After merging the tip tree, all my linux-next builds took si
Hi Will,
On Thu, 21 May 2020 18:35:22 +0100 Will Deacon wrote:
>
> [+Marco and Boris]
>
> On Fri, May 22, 2020 at 03:31:19AM +1000, Stephen Rothwell wrote:
> > After merging the tip tree, all my linux-next builds took signficantly
> > longer and used much more memory. In some cases, builds woul
Hi Stephen,
[+Marco and Boris]
On Fri, May 22, 2020 at 03:31:19AM +1000, Stephen Rothwell wrote:
> After merging the tip tree, all my linux-next builds took signficantly
> longer and used much more memory. In some cases, builds would seg fault
> due to running out of memory :-(
>
> I have event
Hi Ingo,
On Mon, 21 Oct 2019 07:51:41 +0200 Ingo Molnar wrote:
>
> Hm, that was a weird merge mishap - sorry about that, should go away in
> the next -next iteration.
Thanks.
--
Cheers,
Stephen Rothwell
pgp3bI3wEmsAy.pgp
Description: OpenPGP digital signature
* Stephen Rothwell wrote:
> Hi all,
>
> After merging the tip tree, today's linux-next build (native perf)
> failed like this:
>
> make: execvp: ./check-headers.sh: Permission denied
>
> Caused by commit
>
> 05f2f277053d ("Merge branch 'x86/core'")
>
> which somehow removed execute permi
On Thu, Oct 10, 2019 at 10:23:21PM +1100, Stephen Rothwell wrote:
> Hi Ingo,
>
> On Thu, 10 Oct 2019 10:02:07 +0200 Ingo Molnar wrote:
> >
> > I suspect -next will have to carry this semantic merge conflict
> > resolution until the DRM tree is merged upstream.
>
> Yep, its not a real problem, I
On Thu, Aug 29, 2019 at 02:24:24PM +0200, Thomas Gleixner wrote:
> On Thu, 29 Aug 2019, Peter Zijlstra wrote:
> > On Thu, Aug 29, 2019 at 04:20:12PM +1000, Stephen Rothwell wrote:
> > > From: Stephen Rothwell
> > > Date: Thu, 29 Aug 2019 16:08:49 +1000
> > > Subject: [PATCH] ASoC: Intel: boards: m
On Thu, 29 Aug 2019, Peter Zijlstra wrote:
> On Thu, Aug 29, 2019 at 04:20:12PM +1000, Stephen Rothwell wrote:
> > From: Stephen Rothwell
> > Date: Thu, 29 Aug 2019 16:08:49 +1000
> > Subject: [PATCH] ASoC: Intel: boards: merge fix for
> > INTEL_FAM6_KABYLAKE_MOBILE -> INTEL_FAM6_KABYLAKE_L chang
On Thu, Aug 29, 2019 at 04:20:12PM +1000, Stephen Rothwell wrote:
> From: Stephen Rothwell
> Date: Thu, 29 Aug 2019 16:08:49 +1000
> Subject: [PATCH] ASoC: Intel: boards: merge fix for
> INTEL_FAM6_KABYLAKE_MOBILE -> INTEL_FAM6_KABYLAKE_L change
>
> Signed-off-by: Stephen Rothwell
> ---
> soun
Hi Ilya,
On Wed, 10 Jul 2019 20:21:33 +0200 Ilya Dryomov wrote:
>
> Yes, that is what I figured would happen. I assume you would keep
> carrying this fixup until the ceph tree is merged.
Of course.
--
Cheers,
Stephen Rothwell
pgp3xqEtkmhJC.pgp
Description: OpenPGP digital signature
On Wed, Jul 10, 2019 at 2:01 AM Stephen Rothwell wrote:
>
> Hi all,
>
> On Tue, 9 Jul 2019 16:54:59 +1000 Stephen Rothwell
> wrote:
> >
> > After merging the tip tree, today's linux-next build (x86_64 allmodconfig)
> > failed like this:
> >
> > drivers/block/rbd.c: In function 'wake_lock_waiters
Hi all,
On Tue, 9 Jul 2019 16:54:59 +1000 Stephen Rothwell
wrote:
>
> After merging the tip tree, today's linux-next build (x86_64 allmodconfig)
> failed like this:
>
> drivers/block/rbd.c: In function 'wake_lock_waiters':
> drivers/block/rbd.c:3933:2: error: implicit declaration of function
>
Hi all,
On Tue, 25 Jun 2019 16:04:32 +1000 Stephen Rothwell
wrote:
>
> After merging the tip tree, today's linux-next build (x86_64 allmodconfig)
> failed like this:
>
> drivers/net/wireless/intersil/p54/txrx.c: In function 'p54_rx_data':
> drivers/net/wireless/intersil/p54/txrx.c:386:28: error
Hi all,
On Tue, 25 Jun 2019 16:04:32 +1000 Stephen Rothwell
wrote:
>
> After merging the tip tree, today's linux-next build (x86_64 allmodconfig)
> failed like this:
>
> drivers/net/wireless/intersil/p54/txrx.c: In function 'p54_rx_data':
> drivers/net/wireless/intersil/p54/txrx.c:386:28: error
Hi David,
On Tue, 2 Jul 2019 12:28:32 +0200 David Sterba wrote:
>
> On Tue, Jul 02, 2019 at 03:33:02PM +1000, Stephen Rothwell wrote:
> > Hi all,
> >
> > After merging the tip tree, today's linux-next build (powerpc
> > ppc64_defconfig) failed like this:
> >
> > fs/btrfs/ctree.c: In function '_
Hi David,
On Tue, 2 Jul 2019 12:28:32 +0200 David Sterba wrote:
>
> I can move the patches out of the for-5.3 branch and send them
> separately after the rename gets merged, they're merely adding the
> assertion and otherwise do not affect the rest of the code.
>
> Fixing that in another way wou
On Tue, Jul 02, 2019 at 03:33:02PM +1000, Stephen Rothwell wrote:
> Hi all,
>
> After merging the tip tree, today's linux-next build (powerpc
> ppc64_defconfig) failed like this:
>
> fs/btrfs/ctree.c: In function '__tree_mod_log_insert':
> fs/btrfs/ctree.c:388:2: error: implicit declaration of fu
Thomas Gleixner writes:
> On Tue, 25 Jun 2019, Stephen Rothwell wrote:
>
>> Hi Kalle,
>>
>> On Tue, 25 Jun 2019 09:23:33 +0300 Kalle Valo wrote:
>> >
>> > Thanks for the report. Any suggestions how to handle this? Or do we let
>> > Linus take care of this?
>>
>> Just let Linus take care of it
On Tue, 25 Jun 2019, Stephen Rothwell wrote:
> Hi Kalle,
>
> On Tue, 25 Jun 2019 09:23:33 +0300 Kalle Valo wrote:
> >
> > Thanks for the report. Any suggestions how to handle this? Or do we let
> > Linus take care of this?
>
> Just let Linus take care of it ... mention it in the pull request ..
Stephen Rothwell writes:
> On Tue, 25 Jun 2019 09:23:33 +0300 Kalle Valo wrote:
>>
>> Thanks for the report. Any suggestions how to handle this? Or do we let
>> Linus take care of this?
>
> Just let Linus take care of it ... mention it in the pull request ...
Thanks, I'll do that.
> I guess Da
Hi Kalle,
On Tue, 25 Jun 2019 09:23:33 +0300 Kalle Valo wrote:
>
> Thanks for the report. Any suggestions how to handle this? Or do we let
> Linus take care of this?
Just let Linus take care of it ... mention it in the pull request ... I guess
DaveM needs to know, right?
--
Cheers,
Stephen Ro
On Tue, 25 Jun 2019, Kalle Valo wrote:
> Stephen Rothwell writes:
> > ---
> > drivers/net/wireless/intersil/p54/txrx.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/drivers/net/wireless/intersil/p54/txrx.c
> > b/drivers/net/wireless/intersil/p54/txrx.c
> > index
Stephen Rothwell writes:
> After merging the tip tree, today's linux-next build (x86_64 allmodconfig)
> failed like this:
>
> drivers/net/wireless/intersil/p54/txrx.c: In function 'p54_rx_data':
> drivers/net/wireless/intersil/p54/txrx.c:386:28: error: implicit declaration
> of function 'ktime_g
Hi Stephen,
On Thu, Aug 09, 2018 at 09:24:20AM +1000, Stephen Rothwell wrote:
> Invalid absolute R_X86_64_32S relocation: __end_rodata_aligned
> /kisskb/src/arch/x86/boot/compressed/Makefile:127: recipe for target
> 'arch/x86/boot/compressed/vmlinux.relocs' failed
>
> Caused by commit
>
> 39d
On Tue, Apr 03, 2018 at 01:39:08PM +0100, David Howells wrote:
> Peter Zijlstra wrote:
>
> > I figured that since there were only a handful of users it wasn't a
> > popular API, also David very much knew of those patches changing it so
> > could easily have pulled in the special tip/sched/wait br
Stephen Rothwell wrote:
> + wait_var_event(&rxnet->nr_calls, !atomic_read(&rxnet->nr_calls));
I would prefer == 0 to ! as it's not really a true/false value.
But apart from that, it's looks okay and you can add my Reviewed-by.
David
Peter Zijlstra wrote:
> I figured that since there were only a handful of users it wasn't a
> popular API, also David very much knew of those patches changing it so
> could easily have pulled in the special tip/sched/wait branch :/
I'm not sure I could, since I have to base on net-next. I'm not
On Tue, Apr 03, 2018 at 03:41:22PM +1000, Stephen Rothwell wrote:
> Caused by commit
>
> 9b8cce52c4b5 ("sched/wait: Remove the wait_on_atomic_t() API")
>
> interacting with commits
>
> d3be4d244330 ("xrpc: Fix potential call vs socket/net destruction race")
> 31f5f9a1691e ("rxrpc: Fix app
* Stephen Rothwell wrote:
> Hi Ingo,
>
> On Wed, 8 Nov 2017 10:18:28 +0100 Ingo Molnar wrote:
> >
> > Note, I created a commit out of this fix, with your SOB - let me know if
> > you have
> > any objections.
>
> Only a small nit - I didn't bisect it, I just figured it out by
> inspection.
Hi Ingo,
On Wed, 8 Nov 2017 10:18:28 +0100 Ingo Molnar wrote:
>
> * Josh Poimboeuf wrote:
>
> > On Wed, Nov 08, 2017 at 01:47:17PM +1100, Stephen Rothwell wrote:
> >
> > Does this fix it?
> >
> > diff --git a/tools/objtool/Makefile b/tools/objtool/Makefile
> > index 6aaed251b4ed..0f94af3cca
On Wed, Nov 08, 2017 at 10:18:28AM +0100, Ingo Molnar wrote:
>
> * Josh Poimboeuf wrote:
>
> > On Wed, Nov 08, 2017 at 01:47:17PM +1100, Stephen Rothwell wrote:
> > > Presumably caused by commit
> > >
> > > 6a77cff819ae ("objtool: Move synced files to their original relative
> > > locations"
Hi Ingo,
On Wed, 8 Nov 2017 10:18:28 +0100 Ingo Molnar wrote:
>
> Note, I created a commit out of this fix, with your SOB - let me know if you
> have
> any objections.
Only a small nit - I didn't bisect it, I just figured it out by
inspection. Unfortunately, I don't have time to do bisections
* Josh Poimboeuf wrote:
> On Wed, Nov 08, 2017 at 01:47:17PM +1100, Stephen Rothwell wrote:
> > Presumably caused by commit
> >
> > 6a77cff819ae ("objtool: Move synced files to their original relative
> > locations")
> >
> > If it matters, this is a cross compilation (PowerPC host) using O=
Hi Josh,
On Tue, 7 Nov 2017 21:01:52 -0600 Josh Poimboeuf wrote:
>
> On Wed, Nov 08, 2017 at 01:47:17PM +1100, Stephen Rothwell wrote:
> > Presumably caused by commit
> >
> > 6a77cff819ae ("objtool: Move synced files to their original relative
> > locations")
> >
> > If it matters, this is a
On Wed, Nov 08, 2017 at 01:47:17PM +1100, Stephen Rothwell wrote:
> Presumably caused by commit
>
> 6a77cff819ae ("objtool: Move synced files to their original relative
> locations")
>
> If it matters, this is a cross compilation (PowerPC host) using O= .
>
> I have used the tip tree from nex
On Wed, Nov 1, 2017 at 3:51 AM, Stephen Rothwell wrote:
> Hi all,
>
> After merging the tip tree, today's linux-next build (x86_64 allmodconfig)
> failed like this:
>
> In file included from include/linux/workqueue.h:8:0,
> from include/linux/srcu.h:34,
> from inc
Hi all,
With the merge window opening, just a reminder that this semantic
conflict still exists.
On Wed, 28 Jun 2017 13:43:10 +1000 Stephen Rothwell
wrote:
>
> After merging the tip tree, today's linux-next build (x86_64 allmodconfig)
> failed like this:
>
> net/bluetooth/hidp/core.c:1241:39:
Hi jeffy,
On Wed, 28 Jun 2017 12:00:19 +0800 jeffy wrote:
>
> commit 50816c48997af857d4bab3dca1aba90339705e96
> Author: Ingo Molnar
> Date: Sun Mar 5 10:33:16 2017 +0100
>
> sched/wait: Standardize internal naming of wait-queue entries
>
>
> changed wait_queue_entry_t to struct wait_qu
Hi Stephen,
On 06/28/2017 11:43 AM, Stephen Rothwell wrote:
Hi all,
After merging the tip tree, today's linux-next build (x86_64 allmodconfig)
failed like this:
net/bluetooth/hidp/core.c:1241:39: error: unknown type name 'wait_queue_t'
static int hidp_session_wake_function(wait_queue_t *wait
* Stephen Rothwell wrote:
> Hi all,
>
> After merging the tip tree, today's linux-next build (arm
> multi_v7_defconfig) failed like this:
>
> kernel/tracepoint.c: In function 'tracepoint_remove_func':
> kernel/tracepoint.c:253:4: error: implicit declaration of function
> 'static_key_slow_dec_
On 05.04.2017 06:36, Stephen Rothwell wrote:
Hi all,
After merging the tip tree, today's linux-next build (arm
multi_v7_defconfig) failed like this:
drivers/gpu/built-in.o:(__tracepoints+0x64): multiple definition of
`__tracepoint_remove_device_from_group'
drivers/iommu/built-in.o:(__tracepoin
Hi all,
On Wed, 7 Dec 2016 19:56:32 +0100 Ingo Molnar wrote:
>
> * Arnaldo Carvalho de Melo wrote:
>
> > I'll push it today, will stop processing other stuff now and prepare a
> > pull request,
>
> Thanks - I pushed the fixes towards linux-next, so tomorrow's (today's)
> linux-next
> build
* Arnaldo Carvalho de Melo wrote:
> Em Wed, Dec 07, 2016 at 09:12:15AM +0100, Jiri Olsa escreveu:
> > On Wed, Dec 07, 2016 at 08:45:14AM +0100, Ingo Molnar wrote:
> >
> > SNIP
> >
> > > * Stephen Rothwell wrote:
> > >
> > > > Hi all,
> > > >
> > > > After merging the tip tree, today's linux
Em Wed, Dec 07, 2016 at 09:12:15AM +0100, Jiri Olsa escreveu:
> On Wed, Dec 07, 2016 at 08:45:14AM +0100, Ingo Molnar wrote:
>
> SNIP
>
> > * Stephen Rothwell wrote:
> >
> > > Hi all,
> > >
> > > After merging the tip tree, today's linux-next build (powerpc64le perf)
> > > failed like this:
>
On Wed, Dec 07, 2016 at 08:45:14AM +0100, Ingo Molnar wrote:
SNIP
> * Stephen Rothwell wrote:
>
> > Hi all,
> >
> > After merging the tip tree, today's linux-next build (powerpc64le perf)
> > failed like this:
> >
> > LINK /home/sfr/next/perf/fixdep
> > /bin/sh: 1: /home/sfr/next/perf//
Cc:-ing Arnaldo, Jiri, Wang Nan and Peter Foley - bug report quoted below.
This bug/race might have been introduced in the latest tooling bits:
34c4a42791bb Merge tag 'perf-core-for-mingo-20161205' of
git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux into perf/core
Which included thes
lnar; H. Peter Anvin; Peter Zijlstra; linux-
> > n...@vger.kernel.org; linux-kernel@vger.kernel.org; Denys Vlasenko; Chen, Yu
> > C
> > Subject: Re: linux-next: build failure after merge of the tip tree
> >
> > On Thursday, September 29, 2016 01:20:07 PM Stephen Ro
.kernel.org; Denys Vlasenko; Chen, Yu
> C
> Subject: Re: linux-next: build failure after merge of the tip tree
>
> On Thursday, September 29, 2016 01:20:07 PM Stephen Rothwell wrote:
> > Hi all,
> >
> > After merging the tip tree, today's linux-next build (x86_64
>
On Thursday, September 29, 2016 01:20:07 PM Stephen Rothwell wrote:
> Hi all,
>
> After merging the tip tree, today's linux-next build (x86_64 allmodconfig)
> failed like this:
>
> arch/x86/power/hibernate_64.c: In function 'hibernation_e820_save':
> arch/x86/power/hibernate_64.c:236:15: error: p
On 21-09-16, 13:23, Stephen Rothwell wrote:
> Hi all,
>
> After merging the tip tree, today's linux-next build (arm
> multi_v7_defconfig) failed like this:
>
> drivers/cpufreq/cpufreq.c:1324:12: error: conflicting types for
> 'cpufreq_offline'
> static int cpufreq_offline(unsigned int cpu)
>
[linux-next: build failure after merge of the tip tree] On 18/07/2016 (Mon
18:29) Stephen Rothwell wrote:
> Hi all,
>
> After merging the tip tree, today's linux-next build (x86_64 allnoconfig)
> failed like this:
>
> In file included from arch/x86/kernel/x8664_ksyms_64.c:10:0:
> arch/x86/inclu
On Tue, Jul 05, 2016 at 10:25:12AM +0200, Peter Zijlstra wrote:
> On Tue, Jul 05, 2016 at 01:53:03PM +1000, Stephen Rothwell wrote:
> > diff --git a/drivers/gpu/drm/i915/i915_gem.c
> > b/drivers/gpu/drm/i915/i915_gem.c
> > index d3502c0603e5..1f91f187b2a8 100644
> > --- a/drivers/gpu/drm/i915/i915
On Tue, Jul 05, 2016 at 01:53:03PM +1000, Stephen Rothwell wrote:
> diff --git a/drivers/gpu/drm/i915/i915_gem.c b/drivers/gpu/drm/i915/i915_gem.c
> index d3502c0603e5..1f91f187b2a8 100644
> --- a/drivers/gpu/drm/i915/i915_gem.c
> +++ b/drivers/gpu/drm/i915/i915_gem.c
> @@ -3290,7 +3290,7 @@ i915_g
On Mon, Apr 18, 2016 at 10:24:02AM -0300, Arnaldo Carvalho de Melo wrote:
> Em Sun, Apr 17, 2016 at 03:04:05PM +0200, Jiri Olsa escreveu:
> > On Sun, Apr 17, 2016 at 02:12:07PM +0200, Jiri Olsa wrote:
> > > On Fri, Apr 15, 2016 at 06:28:31PM -0300, Arnaldo Carvalho de Melo wrote:
> > > > Em Fri, Ap
Em Sun, Apr 17, 2016 at 03:04:05PM +0200, Jiri Olsa escreveu:
> On Sun, Apr 17, 2016 at 02:12:07PM +0200, Jiri Olsa wrote:
> > On Fri, Apr 15, 2016 at 06:28:31PM -0300, Arnaldo Carvalho de Melo wrote:
> > > Em Fri, Apr 15, 2016 at 06:15:42PM -0300, Arnaldo Carvalho de Melo
> > > escreveu:
> > > >
On Sun, Apr 17, 2016 at 02:12:07PM +0200, Jiri Olsa wrote:
> On Fri, Apr 15, 2016 at 06:28:31PM -0300, Arnaldo Carvalho de Melo wrote:
> > Em Fri, Apr 15, 2016 at 06:15:42PM -0300, Arnaldo Carvalho de Melo escreveu:
> > > Em Thu, Apr 14, 2016 at 12:14:18PM +1000, Stephen Rothwell escreveu:
> > > >
On Fri, Apr 15, 2016 at 06:28:31PM -0300, Arnaldo Carvalho de Melo wrote:
> Em Fri, Apr 15, 2016 at 06:15:42PM -0300, Arnaldo Carvalho de Melo escreveu:
> > Em Thu, Apr 14, 2016 at 12:14:18PM +1000, Stephen Rothwell escreveu:
> > > Hi all,
> > >
> > > After merging the tip tree, today's linux-next
Em Fri, Apr 15, 2016 at 06:15:42PM -0300, Arnaldo Carvalho de Melo escreveu:
> Em Thu, Apr 14, 2016 at 12:14:18PM +1000, Stephen Rothwell escreveu:
> > Hi all,
> >
> > After merging the tip tree, today's linux-next build (powerpc64le perf)
> > failed like this:
> >
> > make[3]: *** No rule to mak
Em Thu, Apr 14, 2016 at 12:14:18PM +1000, Stephen Rothwell escreveu:
> Hi all,
>
> After merging the tip tree, today's linux-next build (powerpc64le perf)
> failed like this:
>
> make[3]: *** No rule to make target
> '/home/sfr/next/perf/arch/x86/include/generated/asm/syscalls_64.c', needed by
Em Thu, Apr 14, 2016 at 10:55:47PM +1000, Michael Ellerman escreveu:
> On Thu, 2016-04-14 at 09:35 -0300, Arnaldo Carvalho de Melo wrote:
> > Em Thu, Apr 14, 2016 at 12:14:18PM +1000, Stephen Rothwell escreveu:
> > > Hi all,
> > >
> > > After merging the tip tree, today's linux-next build (powerpc
On Thu, 2016-04-14 at 09:35 -0300, Arnaldo Carvalho de Melo wrote:
> Em Thu, Apr 14, 2016 at 12:14:18PM +1000, Stephen Rothwell escreveu:
> > Hi all,
> >
> > After merging the tip tree, today's linux-next build (powerpc64le perf)
> > failed like this:
> >
> > make[3]: *** No rule to make target
Em Thu, Apr 14, 2016 at 12:14:18PM +1000, Stephen Rothwell escreveu:
> Hi all,
>
> After merging the tip tree, today's linux-next build (powerpc64le perf)
> failed like this:
>
> make[3]: *** No rule to make target
> '/home/sfr/next/perf/arch/x86/include/generated/asm/syscalls_64.c', needed by
1 - 100 of 202 matches
Mail list logo
