public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: vsntk18@gmail.com
To: ashish.kalra@amd.com
Cc: Sairaj.ArunKodilkar@amd.com, Vasant.Hegde@amd.com,
	davem@davemloft.net, herbert@gondor.apana.org.au,
	iommu@lists.linux.dev, john.allen@amd.com, joro@8bytes.org,
	kvm@vger.kernel.org, linux-crypto@vger.kernel.org,
	linux-kernel@vger.kernel.org, michael.roth@amd.com,
	pbonzini@redhat.com, robin.murphy@arm.com, seanjc@google.com,
	suravee.suthikulpanit@amd.com, thomas.lendacky@amd.com,
	will@kernel.org
Subject: Re: [PATCH v6 3/4] crypto: ccp: Skip SEV and SNP INIT for kdump boot
Date: Wed, 29 Oct 2025 11:43:42 +0100	[thread overview]
Message-ID: <20251029104342.47980-1-vsntk18@gmail.com> (raw)
In-Reply-To: <d884eff5f6180d8b8c6698a6168988118cf9cba1.1756157913.git.ashish.kalra@amd.com>

Hi,

   these changes seem to have been overwritten after
   459daec42ea0c("crypto: ccp - Cache SEV platform status and platform state")
   has been merged upstream.

   I can send a patch if that's not been done already. Please let me know.

Thanks,
Vasant


  reply	other threads:[~2025-10-29 10:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-25 21:45 [PATCH v6 0/4] Add host kdump support for SNP Ashish Kalra
2025-08-25 21:46 ` [PATCH v6 1/4] iommu/amd: Add support to remap/unmap IOMMU buffers for kdump Ashish Kalra
2025-08-25 21:46 ` [PATCH v6 2/4] iommu/amd: Reuse device table " Ashish Kalra
2025-08-25 21:46 ` [PATCH v6 3/4] crypto: ccp: Skip SEV and SNP INIT for kdump boot Ashish Kalra
2025-10-29 10:43   ` vsntk18 [this message]
2025-10-29 14:30     ` Kalra, Ashish
2025-08-25 21:46 ` [PATCH v6 4/4] iommu/amd: Skip enabling command/event buffers for kdump Ashish Kalra
2025-09-05 12:45 ` [PATCH v6 0/4] Add host kdump support for SNP Joerg Roedel

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=20251029104342.47980-1-vsntk18@gmail.com \
    --to=vsntk18@gmail.com \
    --cc=Sairaj.ArunKodilkar@amd.com \
    --cc=Vasant.Hegde@amd.com \
    --cc=ashish.kalra@amd.com \
    --cc=davem@davemloft.net \
    --cc=herbert@gondor.apana.org.au \
    --cc=iommu@lists.linux.dev \
    --cc=john.allen@amd.com \
    --cc=joro@8bytes.org \
    --cc=kvm@vger.kernel.org \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michael.roth@amd.com \
    --cc=pbonzini@redhat.com \
    --cc=robin.murphy@arm.com \
    --cc=seanjc@google.com \
    --cc=suravee.suthikulpanit@amd.com \
    --cc=thomas.lendacky@amd.com \
    --cc=will@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