qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Yong Huang <yong.huang@smartx.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: qemu-devel <qemu-devel@nongnu.org>,
	"Kevin Wolf" <kwolf@redhat.com>,
	"Daniel P . Berrangé" <berrange@redhat.com>,
	"Hanna Reitz" <hreitz@redhat.com>,
	"Eric Blake" <eblake@redhat.com>
Subject: Re: [PATCH RESEND v3 06/10] block: Support detached LUKS header creation using blockdev-create
Date: Thu, 11 Jan 2024 23:52:20 +0800	[thread overview]
Message-ID: <CAK9dgmZR2Pyaj1ECp8wF9RV_WFvAGN8DHgy0MoNq_+hHbbe4fA@mail.gmail.com> (raw)
In-Reply-To: <87o7dsufrk.fsf@pond.sub.org>

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

On Thu, Jan 11, 2024 at 10:05 PM Markus Armbruster <armbru@redhat.com>
wrote:

> Fails to compile for me:
>
> ../block/crypto.c: In function ‘block_crypto_co_create_luks’:
> ../block/crypto.c:784:1: error: control reaches end of non-void function
> [-Werror=return-type]
>   784 | }
>       | ^
>
>
Ok, I'll check it out and fix it in the next version.

By the way, I'm stuck with some other work, so version 4 might not be
finished for
a few weeks, but I'll get to it as soon as I can.

Thanks,
Yong

-- 
Best regards

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

  reply	other threads:[~2024-01-11 15:55 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-25  5:45 [PATCH RESEND v3 00/10] Support generic Luks encryption Hyman Huang
2023-12-25  5:45 ` [PATCH RESEND v3 01/10] crypto: Introduce option and structure for detached LUKS header Hyman Huang
2024-01-11 14:35   ` Markus Armbruster
2024-01-11 14:58     ` Daniel P. Berrangé
2024-01-11 16:02       ` Yong Huang
2023-12-25  5:45 ` [PATCH RESEND v3 02/10] crypto: Support generic LUKS encryption Hyman Huang
2024-01-04 14:39   ` Daniel P. Berrangé
2024-01-07 11:56     ` Yong Huang
2023-12-25  5:45 ` [PATCH RESEND v3 03/10] qapi: Make parameter 'file' optional for BlockdevCreateOptionsLUKS Hyman Huang
2024-01-04 14:40   ` Daniel P. Berrangé
2023-12-25  5:45 ` [PATCH RESEND v3 04/10] crypto: Introduce creation option and structure for detached LUKS header Hyman Huang
2024-01-04 14:51   ` Daniel P. Berrangé
2024-01-07 11:58     ` Yong Huang
2023-12-25  5:45 ` [PATCH RESEND v3 05/10] crypto: Mark the payload_offset_sector invalid " Hyman Huang
2024-01-04 14:48   ` Daniel P. Berrangé
2023-12-25  5:45 ` [PATCH RESEND v3 06/10] block: Support detached LUKS header creation using blockdev-create Hyman Huang
2024-01-04 14:47   ` Daniel P. Berrangé
2024-01-11 14:05   ` Markus Armbruster
2024-01-11 15:52     ` Yong Huang [this message]
2023-12-25  5:45 ` [PATCH RESEND v3 07/10] block: Support detached LUKS header creation using qemu-img Hyman Huang
2023-12-25  5:45 ` [PATCH RESEND v3 08/10] crypto: Introduce 'detached-header' field in QCryptoBlockInfoLUKS Hyman Huang
2024-01-04 14:59   ` Daniel P. Berrangé
2023-12-25  5:45 ` [PATCH RESEND v3 09/10] tests: Add detached LUKS header case Hyman Huang
2023-12-25  5:45 ` [PATCH RESEND v3 10/10] MAINTAINERS: Add section "Detached LUKS header" Hyman Huang

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=CAK9dgmZR2Pyaj1ECp8wF9RV_WFvAGN8DHgy0MoNq_+hHbbe4fA@mail.gmail.com \
    --to=yong.huang@smartx.com \
    --cc=armbru@redhat.com \
    --cc=berrange@redhat.com \
    --cc=eblake@redhat.com \
    --cc=hreitz@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=qemu-devel@nongnu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).