All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mariusz Tkaczyk <mariusz.tkaczyk@linux.intel.com>
To: Blazej Kucman <blazej.kucman@intel.com>
Cc: jes@trained-monkey.org, linux-raid@vger.kernel.org
Subject: Re: [PATCH v2 0/6] Disk encryption status handling
Date: Tue, 2 Apr 2024 08:32:01 +0200	[thread overview]
Message-ID: <20240402083201.00003023@linux.intel.com> (raw)
In-Reply-To: <20240322115120.12325-1-blazej.kucman@intel.com>

On Fri, 22 Mar 2024 12:51:14 +0100
Blazej Kucman <blazej.kucman@intel.com> wrote:

> The purpose of this series is to add functionality of reading information
> about the encryption status of OPAL NVMe/SATA and SATA drives and use this
> information for purposes of IMSM metadata, which introduces restrictions
> on the possibility of mixing disks with encryption enabled and disabled
> because of security reasons.
> 
> Changes in V2:
> - add separate patch for change location of pr_vrb(),
> - add example results for usage of new feature to commit message in patch 5,
> - adjust commit messages to 75 characters,
> - general fixes after review.
>

No more questions from community..
Applied!

Thanks,
Mariusz

      parent reply	other threads:[~2024-04-02  6:32 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-22 11:51 [PATCH v2 0/6] Disk encryption status handling Blazej Kucman
2024-03-22 11:51 ` [PATCH v2 1/6] mdadm: Move pr_vrb define to mdadm.h Blazej Kucman
2024-03-22 11:51 ` [PATCH v2 2/6] Add reading Opal NVMe encryption information Blazej Kucman
2024-05-15  3:20   ` Xiao Ni
2024-05-15 14:26     ` Blazej Kucman
2024-05-16  9:02       ` Blazej Kucman
2024-03-22 11:51 ` [PATCH v2 3/6] Add reading SATA " Blazej Kucman
2024-03-22 11:51 ` [PATCH v2 4/6] Add key ENCRYPTION_NO_VERIFY to conf Blazej Kucman
2024-03-22 11:51 ` [PATCH v2 5/6] imsm: print disk encryption information Blazej Kucman
2024-03-22 11:51 ` [PATCH v2 6/6] imsm: drive encryption policy implementation Blazej Kucman
2024-04-02  6:32 ` Mariusz Tkaczyk [this message]

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=20240402083201.00003023@linux.intel.com \
    --to=mariusz.tkaczyk@linux.intel.com \
    --cc=blazej.kucman@intel.com \
    --cc=jes@trained-monkey.org \
    --cc=linux-raid@vger.kernel.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.