All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mikko Rapeli <mikko.rapeli@linaro.org>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: Qi.Chen@windriver.com, openembedded-core@lists.openembedded.org,
	Erik Schilling <erik.schilling@linaro.org>,
	Richard Purdie <richard.purdie@linuxfoundation.org>
Subject: Re: [OE-core] [PATCH 1/3] systemd-tools: add recipe
Date: Mon, 2 Sep 2024 13:29:38 +0300	[thread overview]
Message-ID: <ZtWTkiaC-D06aXn_@nuoska> (raw)
In-Reply-To: <CANNYZj-57xLA-UnJ+nJvdpcu=+AgygMPoz2Pjzxs-QE+vxJ=nQ@mail.gmail.com>

Hi,

On Mon, Sep 02, 2024 at 12:17:53PM +0200, Alexander Kanavin wrote:
> Wait. Isn't this ukify.py thingy already provided from
> systemd-boot-native recipe?

Oh, it is. I've somehow missed this. Will switch over to it.

Cheers,

-Mikko


  reply	other threads:[~2024-09-02 10:29 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-02  9:41 [PATCH 0/3] systemd uki support Mikko Rapeli
2024-09-02  9:41 ` [PATCH 1/3] systemd-tools: add recipe Mikko Rapeli
2024-09-02  9:59   ` [OE-core] " Richard Purdie
2024-09-02 10:05     ` Mikko Rapeli
2024-09-02 10:17       ` Alexander Kanavin
2024-09-02 10:29         ` Mikko Rapeli [this message]
2024-09-02 10:36         ` Erik Schilling
2024-09-02  9:41 ` [PATCH 2/3] bitbake.conf: add getopt to HOSTTOOLS Mikko Rapeli
2024-09-02 10:09   ` [OE-core] " Peter Kjellerstedt
2024-09-02 10:15     ` Alexander Kanavin
2024-09-02 10:27       ` Mikko Rapeli
2024-09-02 10:34         ` Alexander Kanavin
     [not found]       ` <17F1667FB4E21297.30681@lists.openembedded.org>
2024-09-02 10:35         ` Mikko Rapeli
2024-09-02 10:15     ` Mikko Rapeli
2024-09-02  9:41 ` [PATCH 3/3] uki.bbclass: add class for building Unified Kernel Images (UKI) Mikko Rapeli
2024-09-02 10:36   ` Erik Schilling

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=ZtWTkiaC-D06aXn_@nuoska \
    --to=mikko.rapeli@linaro.org \
    --cc=Qi.Chen@windriver.com \
    --cc=alex.kanavin@gmail.com \
    --cc=erik.schilling@linaro.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.