All of lore.kernel.org
 help / color / mirror / Atom feed
From: Markus Volk <f_l_k@t-online.de>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: raj.khem@gmail.com, openembedded-devel@lists.openembedded.org
Subject: Re: [oe] [meta-oe][PATCH] iwd: use internal ell
Date: Sat, 07 Sep 2024 20:23:51 +0200	[thread overview]
Message-ID: <RFGGJS.TVMQIX4IAUA23@t-online.de> (raw)
In-Reply-To: <CA+chaQdHMh6W920EHbHvE4UfrfDAacWS6C_4X8gsU=mahrkFAQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 883 bytes --]

On Sat, Sep 7 2024 at 05:44:19 PM +02:00:00, Martin Jansa 
<martin.jansa@gmail.com> wrote:
> explicitly the external on (from oe-core) since
> <https://git.openembedded.org/openembedded-core/commit/meta/recipes-connectivity/ofono?id=3683f524dc60325b3f3b1bc3a32e70a41064ae03>

Understand. I also know that bluez5 uses ell when PACKAGECONFIG is 
enabled for either mesh or btpclient. But that's not the default. So 
for consistency, maybe it would be good to keep it external for all 
three?

I'm not sure about this change either, but wanted to bring it up for 
discussion because it always feels a bit like groundhog day with 
iwd/ell.

I'm not that familiar with investigating sstate cache reuse issues. I'm 
willing to learn more about it, but right now I don't know what exact 
files I would need to compare, or is there something like a tool that 
can be used for this purpose?


[-- Attachment #2: Type: text/html, Size: 1241 bytes --]

  reply	other threads:[~2024-09-07 18:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-07  8:34 [meta-oe][PATCH] iwd: use internal ell Markus Volk
2024-09-07 15:23 ` [oe] " Khem Raj
2024-09-07 15:44   ` Martin Jansa
2024-09-07 18:23     ` Markus Volk [this message]
2024-09-07 19:56       ` Khem Raj
2024-09-07 20:06         ` Markus Volk

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=RFGGJS.TVMQIX4IAUA23@t-online.de \
    --to=f_l_k@t-online.de \
    --cc=martin.jansa@gmail.com \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=raj.khem@gmail.com \
    /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.