Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Yoann Congal" <yoann.congal@smile.fr>
To: "Jaipaul Cheernam" <jaipaul.cheernam@est.tech>
Cc: "openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>,
	<bruce.ashfield@gmail.com>
Subject: Re: Request for linux-yocto 6.18.54 upgrade on wrynose
Date: Thu, 15 Oct 2026 17:48:08 +0200	[thread overview]
Message-ID: <DM5J37X3OBGX.LF4NUVEN635T@smile.fr> (raw)
In-Reply-To: <39eccd41-ee64-4500-b28e-6fb364089efa@est.tech>

On Thu Oct 15, 2026 at 2:12 PM CEST, Jaipaul Cheernam wrote:
> Hi Yoann,
>
> I encounter an issue with linux-yocto version 6.18.52 on wrynose with 
> TUI disabled for perf.
>
> In short due to "e97bd4417010  "perf annotate: Fix build with 
> NO_SLANG=1" commit.
>
> builtin-annotate.c:523: error: too few arguments to function
>
>    'hist_entry__tui_annotate'; expected 4, have 3
>
>
> Kernel 6.18.54 already fixes this — it just reverts that bad commit:
>
> 8c3b2bf7f39c7  Revert "perf annotate: Fix build with NO_SLANG=1"
>
> But  wrynose branch is still  on **6.18.52**, which is the broken one.
>
> May I know do we have plans to upgrade wrynose to 6.18.54 ?
>
> Here is 6.18.54 upgrade on master from Bruce.
>
> https://patchwork.yoctoproject.org/project/oe-core/patch/20260929154516.2507960-1-bruce.ashfield@gmail.com/

Hello,

I simply missed that backport. Thanks for the reminder, I've added it to
the next wrynose cycle. Expect it in the next 2 weeks.

Regards,
-- 
Yoann Congal
Smile ECS



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

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-15 12:12 Request for linux-yocto 6.18.54 upgrade on wrynose Jaipaul Cheernam
2026-10-15 15:48 ` Yoann Congal [this message]

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=DM5J37X3OBGX.LF4NUVEN635T@smile.fr \
    --to=yoann.congal@smile.fr \
    --cc=bruce.ashfield@gmail.com \
    --cc=jaipaul.cheernam@est.tech \
    --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