Re: [linux-yocto] [PATCH 1/2] netfilter/netfilter.cfg: remove CONFIG_NF_NAT_IPV4
Hi Bruce, Both these changes are only for master and are specific to v5.1. On Thu, 2019-05-16 at 10:26 +0800, Anuj Mittal wrote: > This has been removed starting v5.1 and nf_nat_ipv4,6 have been > merged > in nat core. > > https://github.com/torvalds/linux/commit/3bf195ae6037e310d693ff3313401cfaf1261b71 > > Signed-off-by: Anuj Mittal > --- > features/netfilter/netfilter.cfg | 1 - > 1 file changed, 1 deletion(-) > > diff --git a/features/netfilter/netfilter.cfg > b/features/netfilter/netfilter.cfg > index 3d61881e..820c222e 100644 > --- a/features/netfilter/netfilter.cfg > +++ b/features/netfilter/netfilter.cfg > @@ -77,7 +77,6 @@ CONFIG_IP_NF_FILTER=m > CONFIG_IP_NF_TARGET_REJECT=m > CONFIG_NF_NAT=m > CONFIG_NF_NAT_NEEDED=y > -CONFIG_NF_NAT_IPV4=m > CONFIG_IP_NF_NAT=m > CONFIG_IP_NF_TARGET_SYNPROXY=m > CONFIG_IP_NF_TARGET_MASQUERADE=m > -- > 2.20.1 > -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
[linux-yocto] [PATCH 2/2] fs/ext4.cfg: remove EXT4_FS_ENCRYPTION and EXT4_ENCRYPTION
These have been removed and are now controlled by CONFIG_FS_ENCRYPTION which is enabled by standard/preempt-rt.cfg. https://github.com/torvalds/linux/commit/643fa9612bf1a29153eee46fd398117632f93cbe Signed-off-by: Anuj Mittal --- cfg/fs/ext4.cfg | 2 -- 1 file changed, 2 deletions(-) diff --git a/cfg/fs/ext4.cfg b/cfg/fs/ext4.cfg index 5d4e2c68..430d265b 100644 --- a/cfg/fs/ext4.cfg +++ b/cfg/fs/ext4.cfg @@ -1,5 +1,3 @@ CONFIG_EXT4_FS=y CONFIG_EXT4_FS_POSIX_ACL=y CONFIG_EXT4_FS_SECURITY=y -CONFIG_EXT4_ENCRYPTION=y -CONFIG_EXT4_FS_ENCRYPTION=y -- 2.20.1 -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
[linux-yocto] [PATCH 1/2] netfilter/netfilter.cfg: remove CONFIG_NF_NAT_IPV4
This has been removed starting v5.1 and nf_nat_ipv4,6 have been merged in nat core. https://github.com/torvalds/linux/commit/3bf195ae6037e310d693ff3313401cfaf1261b71 Signed-off-by: Anuj Mittal --- features/netfilter/netfilter.cfg | 1 - 1 file changed, 1 deletion(-) diff --git a/features/netfilter/netfilter.cfg b/features/netfilter/netfilter.cfg index 3d61881e..820c222e 100644 --- a/features/netfilter/netfilter.cfg +++ b/features/netfilter/netfilter.cfg @@ -77,7 +77,6 @@ CONFIG_IP_NF_FILTER=m CONFIG_IP_NF_TARGET_REJECT=m CONFIG_NF_NAT=m CONFIG_NF_NAT_NEEDED=y -CONFIG_NF_NAT_IPV4=m CONFIG_IP_NF_NAT=m CONFIG_IP_NF_TARGET_SYNPROXY=m CONFIG_IP_NF_TARGET_MASQUERADE=m -- 2.20.1 -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
[linux-yocto] v4.18.x - stable updates comprising v4.18.38
Bruce, Yocto kernel folks: Here is the next 4.18.x stable update "extension" primarily created for the Yocto project, continuing from the previous v4.18.37 release. There is one trivial one line commit to fix a build error on PPC64 from the MDS patches of v4.18.37 - which was also present in GregKH's stable releases our v4.18.37 was based on. That patch is 1st in the queue if anyone is looking for it. Greg also has the fix now, and so fingers crossed that we don't see any more whole releases for a single bug-fix for months and months. There are about 165 commits here, based on commits chosen from what were used in the 4.19.37 and 4.19.38 stable releases. I had most of this work done before MDS came along, hence the close together releases. There is a slight bias towards networking in the content here; it seems in v4.19, an ipv6 frag issue was best resolved by importing work that combined some ipv4/ipv6 code first. And for 4.18 here, I had to extend that slightly by getting some related commits between 4.18 and 4.19. But after doing that, the related commits played nice together during application, and some basic ping6 tests didn't reveal any issues. I've put this 4.18.x queue through the usual testing; build testing on x86-64/32, ARM-64/32, PPC and MIPS, plus some static analysis and finally some sanity runtime tests on x86-64. I did the signed tag just as per the previously released versions. Please find a signed v4.18.38 tag using this key: http://pgp.mit.edu/pks/lookup?op=vindex&search=0xEBCE84042C07D1D6 in the repo in the kernel.org directory here: https://git.kernel.org/pub/scm/linux/kernel/git/paulg/linux-4.18.y.git/?h=linux-4.18.y git://git.kernel.org/pub/scm/linux/kernel/git/paulg/linux-4.18.y.git for merge to standard/base in linux-yocto-4.18 and then out from there into the other base and BSP branches. For those who are interested, the evolution of the commits is here: https://git.kernel.org/cgit/linux/kernel/git/paulg/longterm-queue-4.18.git/ This repo isn't needed for anything; it just exists for transparency and so people can see the evolution of the raw commits that were originally selected to create this 4.18.x release. Paul. -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] how to add recipe-sysroot-native to PKG_CONFIG_PATH for linux-yocto
On Wed, 15 May 2019 at 03:31, Tong Chen wrote: > +DEPENDS += "openssl-native util-linux-native pkgconfig-native > glib-2.0-native zlib-native" It isn't very clear, is kallsyms a native tool using during build, or is it something for the target? If it's a native tool, then it's tricky. Yocto does not support mixing native and target builds in the same recipe (what if something needs a native glib, and something else needs the target one?); you might want to write a separate -native recipe for the item you want to build. Alex -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
