From: Dave Hansen <dave.hansen@intel.com>
To: Nikolay Borisov <nik.borisov@suse.com>, linux-coco@lists.linux.dev
Cc: x86@kernel.org, dave.hansen@linux.intel.com,
dan.j.williams@intel.com, dionnaglaze@google.com,
sathyanarayanan.kuppuswamy@linux.intel.com
Subject: Re: [PATCH] virt: tdx-guest: Deprecate legacy IOCTL-based interface for quote generation
Date: Wed, 31 Jan 2024 07:27:38 -0800 [thread overview]
Message-ID: <464ff551-5909-42e4-b544-5c68ff86c76c@intel.com> (raw)
In-Reply-To: <e3078be1-397a-4927-966a-acea5561eec8@suse.com>
On 1/30/24 23:28, Nikolay Borisov wrote:
> On 24.01.24 г. 11:38 ч., Nikolay Borisov wrote:
>> IOCTL based interface was the natural choice for interacting with the
>> quote generation machine at a time when there wasn't anything better.
>> Fortunately, now we have a vendor-agnostic, configfs-based one which
>> obviates the need to have the IOCTL-based interface.
>>
>> Gate the relevant code behind a Kconfig option, clearly marking it as
>> deprecated as well as introduce a runtime warning.
>>
>> Signed-off-by: Nikolay Borisov <nik.borisov@suse.com>
>
> Ping?
There is no clear consensus from this changelog, nor the tags about this
approach. It would be much appreciated if you could make this changelog
more freestanding and make it clear that this approach is acceptable to
both the authors and users of the code you are modifying.
next prev parent reply other threads:[~2024-01-31 15:27 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-24 9:38 [PATCH] virt: tdx-guest: Deprecate legacy IOCTL-based interface for quote generation Nikolay Borisov
2024-01-31 7:28 ` Nikolay Borisov
2024-01-31 15:27 ` Dave Hansen [this message]
2024-01-31 18:18 ` Nikolay Borisov
2024-01-31 19:05 ` Dave Hansen
2024-02-01 4:14 ` Haitao Huang
2024-02-01 4:55 ` Dan Williams
2024-01-31 7:48 ` Kuppuswamy Sathyanarayanan
2024-01-31 19:50 ` Dan Williams
2024-01-31 19:56 ` Nikolay Borisov
2024-01-31 20:44 ` Kuppuswamy Sathyanarayanan
2024-01-31 21:00 ` Daniel P. Berrangé
2024-01-31 21:12 ` Dan Williams
2024-02-01 2:52 ` Kuppuswamy Sathyanarayanan
2024-02-01 8:15 ` Daniel P. Berrangé
2024-01-31 21:09 ` Dan Williams
2024-02-08 13:42 ` Mikko Ylinen
2024-02-09 2:23 ` Dan Middleton
2024-02-12 23:12 ` Dan Williams
2024-01-31 20:23 ` Dan Williams
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=464ff551-5909-42e4-b544-5c68ff86c76c@intel.com \
--to=dave.hansen@intel.com \
--cc=dan.j.williams@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=dionnaglaze@google.com \
--cc=linux-coco@lists.linux.dev \
--cc=nik.borisov@suse.com \
--cc=sathyanarayanan.kuppuswamy@linux.intel.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;
as well as URLs for NNTP newsgroup(s).