I noticed you don't have the following lines (or some of the other
related security ones) in your .config.
CONFIG_SECURITY=y
CONFIG_SECURITY_WRITABLE_HOOKS=y
Seems like we need a 'depends on SECURITY' line (or something like
that) in security/safesetid/Kconfig -- let me see if that fixes things
On 1/28/19 10:11 PM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20190125:
>
on i386:
ld: security/integrity/digsig.o: in function `integrity_init_keyring':
digsig.c:(.init.text+0x14b): undefined reference to `set_platform_trusted_keys'
Full randconfig file is attached.
--
~Randy
On 1/28/19 10:11 PM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20190125:
>
on x86_64:
ld: security/safesetid/lsm.o:(.data+0x10): undefined reference to
`security_hook_heads'
ld: security/safesetid/lsm.o:(.data+0x38): undefined reference to
`security_hook_heads'
ld:
On 1/29/19 8:57 AM, Srinivas Kandagatla wrote:
>
>
> https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git/commit/?h=for-5.1=a8233b6c1972e1959cf84a021aeb61ddcd23cc26
>
> This should fix the issue! It should be in next today!
Looks good. Thanks.
> Thanks,
> srini
>
>
> On
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git/commit/?h=for-5.1=a8233b6c1972e1959cf84a021aeb61ddcd23cc26
This should fix the issue! It should be in next today!
Thanks,
srini
On 29/01/2019 16:50, Randy Dunlap wrote:
On 1/28/19 10:11 PM, Stephen Rothwell wrote:
Hi all,
Hi all,
Changes since 20190125:
The vfs tree still had its build failure for which I applied a patch.
The net-next tree gained a build failure for which I applied a patch.
The mtd tree gained a conflict against Linus' tree.
The char-misc tree gained conflicts against the qcom tree.
Non-merge
Hi all,
Please do not add any v4.17 material to your linux-next included branches
until after v4.16-rc1 has been released.
Changes since 20180126:
The f2fs tree still had its build failure due to an interaction with
the btrfs tree for which I reverted a commit.
The pci tree lost its build
Hi all,
Please do not add any v4.17 material to your linux-next included branches
until after v4.16-rc1 has been released.
Changes since 20180126:
The f2fs tree still had its build failure due to an interaction with
the btrfs tree for which I reverted a commit.
The pci tree lost its build
Hi all,
Changes since 20160128:
The gpio tree gained a build failure so I used the version from
next-20160128.
The aio tree still had a build failure so I used the version from
next-20160111.
I added 2 supplied patches to the akpm-current tree to fix build
problems.
Non-merge commits
Hi all,
Changes since 20160128:
The gpio tree gained a build failure so I used the version from
next-20160128.
The aio tree still had a build failure so I used the version from
next-20160111.
I added 2 supplied patches to the akpm-current tree to fix build
problems.
Non-merge commits
Hi all,
Changes since 20150128:
The drm tree gained a conflict against Linus' tree.
The sound-asoc tree lost its build failure.
The block tree gained a conflict against the l2-mtd tree.
The akpm-current tree gained a conflict against the xen-tip tree.
Non-merge commits (relative to Linus'
Hi all,
Changes since 20150128:
The drm tree gained a conflict against Linus' tree.
The sound-asoc tree lost its build failure.
The block tree gained a conflict against the l2-mtd tree.
The akpm-current tree gained a conflict against the xen-tip tree.
Non-merge commits (relative to Linus'
On Wed, 29 Jan 2014 16:28:55 +1100 Stephen Rothwell
wrote:
>
> Non-merge commits (relative to Linus' tree): 2689
> 3435 files changed, 215376 insertions(+), 61940 deletions(-)
Actually:
Non-merge commits (relative to Linus' tree): 2751
3315 files changed, 222970 insertions(+), 63268
Hi all,
Please do *not* add material destined for v3.15 to your linux-next
included trees until after v3.14-rc1 is released.
This tree fails (more than usual) the powerpc allyesconfig build.
Changes since 20140128:
Linus' tree gained a build failure for which I applied a supplied patch.
The
Hi all,
Please do *not* add material destined for v3.15 to your linux-next
included trees until after v3.14-rc1 is released.
This tree fails (more than usual) the powerpc allyesconfig build.
Changes since 20140128:
Linus' tree gained a build failure for which I applied a supplied patch.
The
On Wed, 29 Jan 2014 16:28:55 +1100 Stephen Rothwell s...@canb.auug.org.au
wrote:
Non-merge commits (relative to Linus' tree): 2689
3435 files changed, 215376 insertions(+), 61940 deletions(-)
Actually:
Non-merge commits (relative to Linus' tree): 2751
3315 files changed, 222970
16 matches
Mail list logo
