public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Baoquan He <bhe@redhat.com>
To: Coiby Xu <coxu@redhat.com>
Cc: kexec@lists.infradead.org, "Ondrej Kozina" <okozina@redhat.com>,
	"Milan Broz" <gmazyland@gmail.com>,
	"Thomas Staudt" <tstaudt@de.ibm.com>,
	"Daniel P . Berrangé" <berrange@redhat.com>,
	"Kairui Song" <ryncsn@gmail.com>,
	"Jan Pazdziora" <jpazdziora@redhat.com>,
	"Pingfan Liu" <kernelfans@gmail.com>,
	"Dave Young" <dyoung@redhat.com>,
	linux-kernel@vger.kernel.org, x86@kernel.org,
	"Dave Hansen" <dave.hansen@intel.com>,
	"Vitaly Kuznetsov" <vkuznets@redhat.com>
Subject: Re: [PATCH v3 0/7] Support kdump with LUKS encryption by reusing LUKS volume keys
Date: Tue, 21 May 2024 11:19:57 +0800	[thread overview]
Message-ID: <ZkwS3UNmjTkK2HeY@MiWiFi-R3L-srv> (raw)
In-Reply-To: <iwx2noaevjat4uzqvagmrwgxgxj3rufanut4gnjte33thx2bdr@r3fhtf45sgrv>

On 05/21/24 at 09:43am, Coiby Xu wrote:
> On Mon, May 20, 2024 at 02:18:09PM +0800, Baoquan He wrote:
> > Please don't add dm-devel@redhat.com in the public list because it's a
> > internal mailing list or aliase. And I got error when replying.
> 
> Thanks for the reminder! Actually it's a public mailing list and you
> can find all emails publicly listed on [1]. I did some research and it
> seems we should email to dm-devel@lists.linux.dev instead. Quoting [2],

I always got this when replying to your patch. Maybe you registered
before.

msmtp: recipient address dm-devel@redhat.com not accepted by the server
msmtp: server message: 550 5.1.1 <dm-devel@redhat.com>: Recipient address rejected: User unknown in local
recipient table


> > To post a message to all the list members (who were subscribed with
> > mail delivery enabled as of 2023.10.20), send email to
> > dm-devel@lists.linux.dev.  You can no longer subscribe to
> > dm-devel@redhat.com, to subscribe to dm-devel@lists.linux.dev please
> > send email to dm-devel+subscribe@lists.linux.dev.
> 
> [1] https://lore.kernel.org/dm-devel/
> [2] https://listman.redhat.com/mailman/listinfo/dm-devel
> 
> -- 
> Best regards,
> Coiby
> 


  reply	other threads:[~2024-05-21  3:20 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-25 10:04 [PATCH v3 0/7] Support kdump with LUKS encryption by reusing LUKS volume keys Coiby Xu
2024-04-25 10:04 ` [PATCH v3 1/7] kexec_file: allow to place kexec_buf randomly Coiby Xu
2024-05-20  6:16   ` Baoquan He
2024-05-21  1:58     ` Coiby Xu
2024-05-21  3:13       ` Baoquan He
2024-05-24  7:22         ` Coiby Xu
2024-04-25 10:04 ` [PATCH v3 2/7] crash_dump: make dm crypt keys persist for the kdump kernel Coiby Xu
2024-04-26 13:10   ` kernel test robot
2024-05-21  3:20     ` Baoquan He
2024-05-23  5:34       ` Coiby Xu
2024-04-25 10:04 ` [PATCH v3 3/7] crash_dump: store dm keys in kdump reserved memory Coiby Xu
2024-05-21  3:42   ` Baoquan He
2024-05-24  7:38     ` Coiby Xu
2024-04-25 10:04 ` [PATCH v3 4/7] crash_dump: reuse saved dm crypt keys for CPU/memory hot-plugging Coiby Xu
2024-05-21  3:48   ` Baoquan He
2024-05-24  7:40     ` Coiby Xu
2024-04-25 10:04 ` [PATCH v3 5/7] crash_dump: retrieve dm crypt keys in kdump kernel Coiby Xu
2024-04-25 10:04 ` [PATCH v3 6/7] x86/crash: pass dm crypt keys to " Coiby Xu
2024-04-25 10:04 ` [PATCH v3 7/7] x86/crash: make the page that stores the dm crypt keys inaccessible Coiby Xu
2024-05-21  3:51   ` Baoquan He
2024-05-24  7:43     ` Coiby Xu
2024-05-20  6:18 ` [PATCH v3 0/7] Support kdump with LUKS encryption by reusing LUKS volume keys Baoquan He
2024-05-21  1:43   ` Coiby Xu
2024-05-21  3:19     ` Baoquan He [this message]
2024-05-30  9:33       ` Dave Young

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=ZkwS3UNmjTkK2HeY@MiWiFi-R3L-srv \
    --to=bhe@redhat.com \
    --cc=berrange@redhat.com \
    --cc=coxu@redhat.com \
    --cc=dave.hansen@intel.com \
    --cc=dyoung@redhat.com \
    --cc=gmazyland@gmail.com \
    --cc=jpazdziora@redhat.com \
    --cc=kernelfans@gmail.com \
    --cc=kexec@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=okozina@redhat.com \
    --cc=ryncsn@gmail.com \
    --cc=tstaudt@de.ibm.com \
    --cc=vkuznets@redhat.com \
    --cc=x86@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox