From: Denis Mukhin <dmukhin@ford.com> 

Amends: 37339ba9ef46 ("automation: Remove XEN_CONFIG_EXPERT leftovers")
Signed-off-by: Denis Mukhin <dmukhin@ford.com>
---
 INSTALL | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/INSTALL b/INSTALL
index c2e756bf4b2b..93be8e5b72db 100644
--- a/INSTALL
+++ b/INSTALL
@@ -33,8 +33,8 @@ small subset of the options.  Attempts to change other options will be
 silently overridden.  The only way to find which configuration options
 are available is to run `make menuconfig' or the like.
 
-You can counter-override this behaviour by setting XEN_CONFIG_EXPERT=y
-in your environment.  However, doing this is not supported and the
+You can counter-override this behaviour by setting CONFIG_EXPERT=y
+in your Kconfig file.  However, doing this is not supported and the
 resulting configurations do not receive security support.  If you set
 this variable there is nothing stopping you setting dangerously
 experimental combinations of features - not even any warnings.
-- 
2.52.0

On 08.01.2026 15:16, dmukhin@xen.org wrote:
> From: Denis Mukhin <dmukhin@ford.com> 
> 
> Amends: 37339ba9ef46 ("automation: Remove XEN_CONFIG_EXPERT leftovers")
> Signed-off-by: Denis Mukhin <dmukhin@ford.com>

Acked-by: Jan Beulich <jbeulich@suse.com>

However, ...

> --- a/INSTALL
> +++ b/INSTALL
> @@ -33,8 +33,8 @@ small subset of the options.  Attempts to change other options will be
>  silently overridden.  The only way to find which configuration options
>  are available is to run `make menuconfig' or the like.

... I don't think what is said up from here is quite right. As a result, ...

> -You can counter-override this behaviour by setting XEN_CONFIG_EXPERT=y
> -in your environment.  However, doing this is not supported and the
> +You can counter-override this behaviour by setting CONFIG_EXPERT=y
> +in your Kconfig file.  However, doing this is not supported and the
>  resulting configurations do not receive security support.  If you set
>  this variable there is nothing stopping you setting dangerously
>  experimental combinations of features - not even any warnings.

... some of this is also in need of updating / correcting.

Jan

On 08.01.2026 15:24, Jan Beulich wrote:
> On 08.01.2026 15:16, dmukhin@xen.org wrote:
>> From: Denis Mukhin <dmukhin@ford.com> 
>>
>> Amends: 37339ba9ef46 ("automation: Remove XEN_CONFIG_EXPERT leftovers")
>> Signed-off-by: Denis Mukhin <dmukhin@ford.com>
> 
> Acked-by: Jan Beulich <jbeulich@suse.com>

Actually no, I withdraw this. It makes little sense to update ...

> However, ...
> 
>> --- a/INSTALL
>> +++ b/INSTALL
>> @@ -33,8 +33,8 @@ small subset of the options.  Attempts to change other options will be
>>  silently overridden.  The only way to find which configuration options
>>  are available is to run `make menuconfig' or the like.
> 
> ... I don't think what is said up from here is quite right. As a result, ...
> 
>> -You can counter-override this behaviour by setting XEN_CONFIG_EXPERT=y
>> -in your environment.  However, doing this is not supported and the
>> +You can counter-override this behaviour by setting CONFIG_EXPERT=y

... just this reference, when things also work differently now (?). (IOW
the original description ...

>> +in your Kconfig file.  However, doing this is not supported and the
>>  resulting configurations do not receive security support.  If you set
>>  this variable there is nothing stopping you setting dangerously
>>  experimental combinations of features - not even any warnings.
> 
> ... some of this is also in need of updating / correcting.

... may or may not have been correct when it was still an env var.)

Jan