From: Pavel Machek <pavel@nabladev.com>
To: "Nobuhiro Iwamatsu (Toshiba)" <iwamatsu@gmail.com>
Cc: jan.kiszka@siemens.com, nobuhiro.iwamatsu.x90@mail.toshiba,
cip-dev@lists.cip-project.org, pavel@nabladev.com,
masami.ichikawa@cybertrust.co.jp, uli@fpond.eu,
chris.paterson2@renesas.com
Subject: Re: [cip-dev] [ANNOUNCE] Release v5.10.249-cip69, v6.1.162-cip51 and v6.12.69-cip17
Date: Fri, 13 Feb 2026 13:09:10 +0100 [thread overview]
Message-ID: <aY8UZpBealEWp0/3@duo.ucw.cz> (raw)
In-Reply-To: <CACe6DC5LCgdoPRddKHO+KwnDw6MSaFCfKHmZPb7R1TNyQhSfqA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 979 bytes --]
Hi!
> > > CIP kernel team has released Linux kernel v5.10.249-cip69, v6.1.162-cip51 and
> > > v6.12.69-cip17.
> > > The linux-5.10.y-cip tree has been updated base version from v5.10.247 to
> > > v5.10.249, the linux-6.1.y-cip tree has been updated base version from v6.1.159
> > > to v6.1.162, and the linux-6.12.y-cip tree has been updated base version from
> > > v6.12.66 to v6.12.69.
> > > This release includes updates for Renesas ARM64 SoCs. Please check the following
> > > information.
> > >
> >
> > Thanks! Did you also trigger the tarball generation, and is just
> > kernel.org a bit slow to perform them?
>
> Hmm, that's a bit odd.
>
> I am executing the tar generation trigger with git push.
> I just confirmed that the trigger was running.
> I will wait a bit, and if the archive is not created, I will ask to
> admin.
Normally, they send some kind of result over email.
Best regards,
Pavel
--
In cooperation with Nabla.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
prev parent reply other threads:[~2026-02-13 12:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-13 2:39 [ANNOUNCE] Release v5.10.249-cip69, v6.1.162-cip51 and v6.12.69-cip17 nobuhiro.iwamatsu.x90
2026-02-13 7:34 ` Jan Kiszka
2026-02-13 11:43 ` [cip-dev] " Nobuhiro Iwamatsu (Toshiba)
2026-02-13 12:09 ` Pavel Machek [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=aY8UZpBealEWp0/3@duo.ucw.cz \
--to=pavel@nabladev.com \
--cc=chris.paterson2@renesas.com \
--cc=cip-dev@lists.cip-project.org \
--cc=iwamatsu@gmail.com \
--cc=jan.kiszka@siemens.com \
--cc=masami.ichikawa@cybertrust.co.jp \
--cc=nobuhiro.iwamatsu.x90@mail.toshiba \
--cc=uli@fpond.eu \
/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