On Sun, 2017-01-29 at 09:12 -0800, Armin Kuster wrote: > diff --git a/recipes-tpm/libtpm/files/fix_dprintf_issue.patch > b/recipes-tpm/libtpm/files/fix_dprintf_issue.patch > new file mode 100644 > index 0000000..25760bb > --- /dev/null > +++ b/recipes-tpm/libtpm/files/fix_dprintf_issue.patch > @@ -0,0 +1,18 @@ > +Upstream-Status: Pending > +Signed-off-by: Armin Kuster <akuster...@gmail.com>
Just wondering: what's your approach regarding "pending" patches? Accept them into the layer, then submit upstream later as time permits? Besides that, the six patches are all fine, so please consider them Signed-off-by: Patrick Ohly <patrick.o...@intel.com> However, when I started using these recipes already before the latest changes, I had to fix quite a few things before the recipes were usable (will send patches shortly): - tcsd from trousers doesn't start because of incorrect ownership of /etc/tcsd.conf - swtpm was more useful for me as a native tool in combination with Stefan's qemu-tpm patches, but couldn't be compiled natively - libtspi.so.1 was not getting installed, causing tpm tools to fail I had the impression that the recipes were mostly in a "they build" kind of state, but not really used much in practice. Is that correct? -- Best Regards, Patrick Ohly The content of this message is my personal opinion only and although I am an employee of Intel, the statements I make here in no way represent Intel's position on the issue, nor am I authorized to speak on behalf of Intel on this matter. -- _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
