Cryptsetup development
 help / color / mirror / Atom feed
From: Anton Lundin <glance@ac2.se>
To: Milan Broz <gmazyland@gmail.com>
Cc: cryptsetup development <cryptsetup@lists.linux.dev>
Subject: Re: [PATCH] Add mbedtls to PKGMODULES
Date: Fri, 5 Jun 2026 19:11:19 +0200	[thread overview]
Message-ID: <aiMDN4xWore5ymZo@accum.se> (raw)
In-Reply-To: <6251d03b-d923-4d64-87a3-1e5aa13c5e94@gmail.com>

On 02 juni, 2026 - Milan Broz wrote:

> Hi,
> 
> I added the patch to MR for review
> https://gitlab.com/cryptsetup/cryptsetup/-/merge_requests/931
> 

I was trying to figure out what the projects workflow was, and it looked
like there were both patches on the mailing list and MR's on gitlab, and
due to me not having a gitlab account since earlier it was just easier
to send it to the ML.

Thanks for the review and merging the code.


//Anton


> On 6/1/26 10:37 PM, Anton Lundin wrote:
> > When cryptsetup is built with --with-crypto_backend=mbedtls, the
> > pkg-config file for libcryptsetup should include mbedtls.
> > ---
> >   configure.ac | 1 +
> >   1 file changed, 1 insertion(+)
> > 
> > diff --git a/configure.ac b/configure.ac
> > index 52ddf11b..260b0ab6 100644
> > --- a/configure.ac
> > +++ b/configure.ac
> > @@ -741,6 +741,7 @@ case $with_crypto_backend in
> >   	openssl) PKGMODULES="$PKGMODULES openssl" ;;
> >   	nss)     PKGMODULES="$PKGMODULES nss" ;;
> >   	nettle)  PKGMODULES="$PKGMODULES nettle" ;;
> > +	mbedtls) PKGMODULES="$PKGMODULES mbedtls" ;;
> >   esac
> >   if test "x$enable_libargon2" = "xyes"; then
> >   	PKGMODULES="$PKGMODULES libargon2"

  reply	other threads:[~2026-06-05 17:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-01 20:37 [PATCH] Add mbedtls to PKGMODULES Anton Lundin
2026-06-02 11:41 ` Milan Broz
2026-06-05 17:11   ` Anton Lundin [this message]
2026-06-05 18:42     ` Milan Broz

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=aiMDN4xWore5ymZo@accum.se \
    --to=glance@ac2.se \
    --cc=cryptsetup@lists.linux.dev \
    --cc=gmazyland@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox