Eudyptula (Was: Kernelnewbies Digest, Vol 89, Issue 14)

2018-04-26 Thread justin . skists
> On 20 April 2018 at 07:28 Aleix Roca Nonell wrote: > > I just wanted to ask the same question. I'm still doing the challenge > but it has been amost two months since I sent my last solution and > there has not been any answer yet (except the usual auto-response of >

Re: [PATCH] sched/fair: Change sched_feat(x) in !CONFIG_SCHED_DEBUG case

2018-04-26 Thread Peter Zijlstra
On Fri, Apr 20, 2018 at 11:29:33PM +0200, Lukas Bulwahn wrote: > > On Fri, 20 Apr 2018, Peter Zijlstra wrote: > > > On Fri, Apr 20, 2018 at 06:29:07PM +0200, Philipp Klocke wrote: > > > The gain is stopping a warning that clutters the output log of clang. > > > > Well, you should not be using

Re: [PATCH] sched/fair: Change sched_feat(x) in !CONFIG_SCHED_DEBUG case

2018-04-26 Thread Peter Zijlstra
On Fri, Apr 20, 2018 at 06:29:07PM +0200, Philipp Klocke wrote: > The gain is stopping a warning that clutters the output log of clang. Well, you should not be using clang anyway. It is known to miscompile the kernel. > To improve readability, one can drop the ifdef-structure and just keep > the

Re: [PATCH] sched/fair: Change sched_feat(x) in !CONFIG_SCHED_DEBUG case

2018-04-26 Thread Peter Zijlstra
Also, please don't cross-post with moderated lists, that's just annoying. ___ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

Re: [PATCH] sched/fair: Change sched_feat(x) in !CONFIG_SCHED_DEBUG case

2018-04-26 Thread Peter Zijlstra
On Mon, Apr 16, 2018 at 10:54:26AM +0200, Philipp Klocke wrote: > This patch is motivated by the clang warning Wconstant-logical-operand, > issued when logically comparing a variable to a constant integer that is > neither 1 nor 0. It happens for sched_feat(x) when sysctl_sched_features > is

Re: Kernelnewbies Digest, Vol 89, Issue 14

2018-04-26 Thread Aleix Roca Nonell
Hello, I just wanted to ask the same question. I'm still doing the challenge but it has been amost two months since I sent my last solution and there has not been any answer yet (except the usual auto-response of task received). Does somebody knows if it is still alive even for old challengers?