Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Mattias Walström" <lazzer@gmail.com>
To: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Cc: buildroot@buildroot.org, "Heiko Thiery" <heiko.thiery@gmail.com>,
	"Jan Kundrát" <jan.kundrat@cesnet.cz>
Subject: Re: [Buildroot] [PATCH v3 1/6] package/sysrepo: bump to version 3.6.11
Date: Mon, 19 May 2025 20:19:47 +0200	[thread overview]
Message-ID: <871psk31ks.fsf@gmail.com> (raw)
In-Reply-To: <20250517113330.1306723e@windsurf>

Thomas Petazzoni via buildroot <buildroot@buildroot.org> writes:

Hi Thomas,

> Hello Mattias,
>
> On Mon, 12 May 2025 19:35:01 +0200
> Mattias Walström <lazzer@gmail.com> wrote:
>
>> Changelog:
>>  several moderate optimizations (@irfanHaslanded)
>>  session push oper data cache
>>  lots of minor bugfixes and improvements
>>
>> Depends on libyang v3.12.2 https://github.com/CESNET/libyang/releases/tag/v3.12.2
>>
>> Signed-off-by: Mattias Walström <lazzer@gmail.com>
>
> Thanks for your patch series. I have applied it all, couple of comments:
>
> - I squashed your patches 4/6 and 5/6 into the libnetconf2 update,
>   because it's really part of the same change
Ok
>
> - I messed up: I did not realize your had PATCH 6/6, and I faced a
>   netopeer2 build failure, so I bumped it, and it's right after pushing
>   that I realized your series did contain the bump
>
Np. It ended up in the correct version, that is the important part.

> - netopeer2 doesn't build when mbedtls is enabled as a crypto backend.
>   Unfortunately, there's no way to tell libnetconf2 to NOT use mbedtls
>   when not available. Can you look into this, reproduce the issue (just
>   build with mbedtls enabled) and work with upstream to fix the issue?
>
I will see what i can do.

BR
 Mattias
> Thanks a lot!
>
> Thomas
> --
> Thomas Petazzoni, co-owner and CEO, Bootlin
> Embedded Linux and Kernel engineering and training
> https://bootlin.com
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2025-05-19 18:19 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-12 17:35 [Buildroot] [PATCH v3 0/6] Bump netopeer2 and its dependencies Mattias Walström
2025-05-12 17:35 ` [Buildroot] [PATCH v3 1/6] package/sysrepo: bump to version 3.6.11 Mattias Walström
2025-05-17  9:33   ` Thomas Petazzoni via buildroot
2025-05-19 18:19     ` Mattias Walström [this message]
2025-05-12 17:35 ` [Buildroot] [PATCH v3 2/6] package/libyang: bump to version 3.12.2 Mattias Walström
2025-05-12 17:35 ` [Buildroot] [PATCH v3 3/6] package/libnetconf2: bump to version 3.7.1 Mattias Walström
2025-05-12 17:35 ` [Buildroot] [PATCH v3 4/6] package/libnetconf2: Update dependencies Mattias Walström
2025-05-12 17:35 ` [Buildroot] [PATCH v3 5/6] package/netopeer2: Update dependencies from libnetconf2 Mattias Walström
2025-05-12 17:35 ` [Buildroot] [PATCH v3 6/6] package/netopeer2: bump to version 2.4.1 Mattias Walström

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=871psk31ks.fsf@gmail.com \
    --to=lazzer@gmail.com \
    --cc=buildroot@buildroot.org \
    --cc=heiko.thiery@gmail.com \
    --cc=jan.kundrat@cesnet.cz \
    --cc=thomas.petazzoni@bootlin.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox