Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: mikko.rapeli@linaro.org, openembedded-core@lists.openembedded.org
Cc: Bruce Ashfield <bruce.ashfield@gmail.com>
Subject: Re: [OE-core] [PATCH 1/4] lttng-modules: update from 2.15.2 to 2.16.0-rc2
Date: Fri, 14 Aug 2026 11:48:32 +0100	[thread overview]
Message-ID: <2b6fbd07547d07ddb00539fc0bf7b8434633f26e.camel@linuxfoundation.org> (raw)
In-Reply-To: <20260814064812.1071873-2-mikko.rapeli@linaro.org>

On Fri, 2026-08-14 at 09:48 +0300, Mikko Rapeli via lists.openembedded.org wrote:
> To support kernel version 7.2. Fixes build error:
> 
> > lttng-syscalls.c: In function 'lttng_syscall_event_enabler_create_event':
> > lttng-syscalls.c:612:17: error: implicit declaration of function 'strncpy' [-Wimplicit-function-declaration]
> >   612 |                 strncpy(ev.name, desc->event_name, LTTNG_KERNEL_ABI_SYM_NAME_LEN - 1);
> >       |                 ^~~~~~~
> > lttng-syscalls.c:101:1: note: include '<string.h>' or provide a declaration of 'strncpy'
> >   100 | #include <instrumentation/syscalls/syscalls_unknown.h>
> >   +++ |+#include <string.h>
> >   101 | #undef TRACE_SYSTEM
> > lttng-syscalls.c:612:17: warning: incompatible implicit declaration of built-in function 'strncpy' [-Wbuiltin-declaration-mismatch]
> >   612 |                 strncpy(ev.name, desc->event_name, LTTNG_KERNEL_ABI_SYM_NAME_LEN - 1);
> >       |                 ^~~~~~~
> > lttng-syscalls.c:612:17: note: include '<string.h>' or provide a declaration of 'strncpy'
> > lttng-syscalls.c:704:17: warning: incompatible implicit declaration of built-in function 'strncpy' [-Wbuiltin-declaration-mismatch]
> >   704 |                 strncpy(ev.name, desc->event_name, LTTNG_KERNEL_ABI_SYM_NAME_LEN - 1);
> >       |                 ^~~~~~~
> > lttng-syscalls.c:704:17: note: include '<string.h>' or provide a declaration of 'strncpy'
> 
> Signed-off-by: Mikko Rapeli <mikko.rapeli@linaro.org>
> ---
>  .../{lttng-modules_2.15.2.bb => lttng-modules_2.16.0-rc2.bb} | 5 +++--
>  1 file changed, 3 insertions(+), 2 deletions(-)
>  rename meta/recipes-kernel/lttng/{lttng-modules_2.15.2.bb => lttng-modules_2.16.0-rc2.bb} (94%)

This probably needs to have a PV of 2.16.0~rc2 else the version sorting
when we upgrade to the release won't work...

Do we know how far off the final release is?

Cheers,

Richard


  reply	other threads:[~2026-08-14 10:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-14  6:48 [PATCH 0/4] Fixes for kernel 7.2 Mikko Rapeli
2026-08-14  6:48 ` [PATCH 1/4] lttng-modules: update from 2.15.2 to 2.16.0-rc2 Mikko Rapeli
2026-08-14 10:48   ` Richard Purdie [this message]
2026-08-14 11:27     ` [OE-core] " Mikko Rapeli
2026-08-14 12:50       ` Bruce Ashfield
2026-08-14  6:48 ` [PATCH 2/4] testexport.bbclass: capture meta/lib/oe Mikko Rapeli
2026-08-14  6:48 ` [PATCH 3/4] kernel-devsrc: copy gen-kernel-hwcaps.sh on arm64 Mikko Rapeli
2026-08-14  6:48 ` [PATCH 4/4] kernel-devsrc: copy kernel/sched/ext directory Mikko Rapeli
2026-08-14 12:48   ` [OE-core] " Bruce Ashfield

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2b6fbd07547d07ddb00539fc0bf7b8434633f26e.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=bruce.ashfield@gmail.com \
    --cc=mikko.rapeli@linaro.org \
    --cc=openembedded-core@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox