Re: [OS-BUILD PATCH] Fix up PREEMPT configs

2021-11-16 Thread Justin M. Forbes (via Email Bridge)
From: Justin M. Forbes on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1500#note_735087605 > Yes, I get that part. I was talking about os-build:50d16ce3099, which has > a one line commit message and says nothing about keeping VOLUNTARY etc. > > The commit message on what

Re: [OS-BUILD PATCH] Fix up PREEMPT configs

2021-11-16 Thread Phil Auld
On Tue, Nov 16, 2021 at 09:19:09PM - Justin M. Forbes (via Email Bridge) wrote: > From: Justin M. Forbes on gitlab.com > https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1500#note_735053347 > > > This commit, or something like it, seems to have gone in but without > > much of a

Re: [OS-BUILD PATCH] Fix up PREEMPT configs

2021-11-16 Thread Justin M. Forbes (via Email Bridge)
From: Justin M. Forbes on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1500#note_735053347 > This commit, or something like it, seems to have gone in but without > much of a commit message. Was that on purpsoe? Yes, there are files in pending-common that go in without

Re: [OS-BUILD PATCH] Fix up PREEMPT configs

2021-11-16 Thread Phil Auld
Hi Justin, On Mon, Nov 15, 2021 at 06:28:11PM - Justin M. Forbes (via Email Bridge) wrote: > From: Justin M. Forbes > > Fix up PREEMPT configs > > While preempt_dynamic was greatly improved at the beginning of the merge > window, the config to make things work was messy and the new

Re: [OS-BUILD PATCH] Fix up PREEMPT configs

2021-11-15 Thread Phil Auld
On Mon, Nov 15, 2021 at 06:28:11PM - Justin M. Forbes (via Email Bridge) wrote: > From: Justin M. Forbes > > Fix up PREEMPT configs > > While preempt_dynamic was greatly improved at the beginning of the merge > window, the config to make things work was messy and the new BEHAVIOUR >

[OS-BUILD PATCH] Fix up PREEMPT configs

2021-11-15 Thread Justin M. Forbes (via Email Bridge)
From: Justin M. Forbes Fix up PREEMPT configs While preempt_dynamic was greatly improved at the beginning of the merge window, the config to make things work was messy and the new BEHAVIOUR configs were confusing to some. With commit a8b76910e465d718effce0cad306a21fa4f3526b the BEHAVIOUR config