Message ID | 20181125211907.9895-2-otavio@ossystems.com.br (mailing list archive) |
---|---|
State | New, archived |
Headers | show |
Series | [01/13] ARM: multi_v7_defconfig: Select PHY_ROCKCHIP_INNO_USB2 | expand |
On Sun, Nov 25, 2018 at 1:19 PM Otavio Salvador <otavio@ossystems.com.br> wrote: > > From: Fabio Berton <fabio.berton@ossystems.com.br> > > Signed-off-by: Fabio Berton <fabio.berton@ossystems.com.br> > Signed-off-by: Otavio Salvador <otavio@ossystems.com.br> Hi Otavio, Thanks for these patches. I don't have a reason to _not_ enable systemd features, but would you mind providing a brief description of what's not working without this change? Is it completely broken, or is it just the random-UID featues that don't work, or something else?. Useful for others to know what's expected to break if someone turns them off, etc. Also, I noticed you posted a series of 13 patches, which includes some dts files for rv1108, some network driver changes and some of these more generic defconfig changes. I would suggest that you split up your patches into independent series where possible, especially when they end up going to different subsystems. Providing suitable cover letters for the series when you post them is also useful to help reviewers by summarizing the series, including changes from last time it was posted, etc. Please address it to the superset of patch receivers on the series. I'm asking for the cover letter because this time I was wondering if there was a reason for the mix of patches so I went looking for it. Maybe there is a need to group them together even though the sub-series seem somewhat independent -- I can't tell from the way they were posted. Thanks! -Olof
Hello Olof, On Sun, Nov 25, 2018 at 8:25 PM Olof Johansson <olof@lixom.net> wrote: > Thanks for these patches. I don't have a reason to _not_ enable > systemd features, but would you mind providing a brief description of > what's not working without this change? Is it completely broken, or is > it just the random-UID featues that don't work, or something else?. > Useful for others to know what's expected to break if someone turns > them off, etc. Thank you for your kindness reviewing this. I am not an experienced Linux kernel contributor so I am going to do some mistakes during this process. We usually follow the required feature set listed on Gentoo wiki[1] as it is usually up to date and avoids a lot of headaches for us when dealing with boot issues with SystemD. 1. https://wiki.gentoo.org/wiki/Systemd#Kernel Do you think mentioning where it has been taken from is enough? > Also, I noticed you posted a series of 13 patches, which includes some > dts files for rv1108, some network driver changes and some of these > more generic defconfig changes. I would suggest that you split up your > patches into independent series where possible, especially when they > end up going to different subsystems. Providing suitable cover letters > for the series when you post them is also useful to help reviewers by > summarizing the series, including changes from last time it was > posted, etc. Please address it to the superset of patch receivers on > the series. I can certainly improve it for the next submission. Should I split them all and tag them v2 to easy it?
diff --git a/arch/arm/configs/multi_v7_defconfig b/arch/arm/configs/multi_v7_defconfig index a8ec309d182a..34c8a745d951 100644 --- a/arch/arm/configs/multi_v7_defconfig +++ b/arch/arm/configs/multi_v7_defconfig @@ -2,7 +2,12 @@ CONFIG_SYSVIPC=y CONFIG_NO_HZ=y CONFIG_HIGH_RES_TIMERS=y CONFIG_CGROUPS=y +CONFIG_CGROUP_BPF=y +CONFIG_NAMESPACES=y +CONFIG_USER_NS=y +CONFIG_CHECKPOINT_RESTORE=y CONFIG_BLK_DEV_INITRD=y +CONFIG_BPF_SYSCALL=y CONFIG_EMBEDDED=y CONFIG_PERF_EVENTS=y CONFIG_MODULES=y