[6/8] ti-sgx-km: rename options to have proper prefix

Message ID 20180513190737.26079-7-thomas.petazzoni@bootlin.com
State Accepted
Commit b54c5464cc57d70af2ac68adcb34dab616bef3be
Headers show
Series
  • Fix the Config.in prefix of a number of options
Related show

Commit Message

Thomas Petazzoni May 13, 2018, 7:07 p.m.
The sub-options of the ti-sgx-km package had their name option
prefixed by BR2_PACKAGE_TI_SGX, while the prefix should be
BR2_PACKAGE_TI_SGX_KM. This commit fixes that, and adds the necessary
Config.in.legacy handling.

Since those options are part of a choice, the legacy handling cannot
select the new name of the options, so the legacy handling only
informs the user of the rename.

Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
---
 Config.in.legacy               | 32 ++++++++++++++++++++++++++++++++
 package/ti-sgx-km/Config.in    | 10 +++++-----
 package/ti-sgx-km/ti-sgx-km.mk |  8 ++++----
 3 files changed, 41 insertions(+), 9 deletions(-)

Comments

Yann E. MORIN May 13, 2018, 7:31 p.m. | #1
Thomas, All,

On 2018-05-13 21:07 +0200, Thomas Petazzoni spake thusly:
> The sub-options of the ti-sgx-km package had their name option
> prefixed by BR2_PACKAGE_TI_SGX, while the prefix should be
> BR2_PACKAGE_TI_SGX_KM. This commit fixes that, and adds the necessary
> Config.in.legacy handling.
> 
> Since those options are part of a choice, the legacy handling cannot
> select the new name of the options, so the legacy handling only
> informs the user of the rename.

As I was explaining on IRC, we /could/ have legacy handling for choices.
This would be done in three parts;

  - the new options replace the old ones in the choice, as we currently
    do (and as is done in this patch);

  - this choice is given a "name" (see below), so we can redefine it
    elsewhere;

  - in the legacy menu, we duplicate the choice with the same "name"
    and the same options, but with a set of "default-if" options.


For example:

    # In bar/Config.in:
    choice BAR
        bool "bar choice"
    config BAR_1
        bool "bar 1"
    config BAR_2
        bool "bar 2"
    endchoice

    # In Config.in.legacy:
    choice BAR
        bool "bar choice"
        default BAR_1 if FOO_1
        default BAR_2 if FOO_2
    config BAR_1
        bool "bar 1"
    config BAR_2
        bool "bar 2"
    endchoice

    config FOO_1
        bool "foo 1 was renamed"
    config FOO_2
        bool "foo 2 was renamed"

(not tested, but it should work).

What is nice with this solution, is that we have the new choice that is
right near the legacy option so we can chek it, and it automatically
gets the old setting.

But I am not too convinced, however, because we do not usually use the
name of a choice elsewhere...

> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>

Acked-by: "Yann E. MORIN" <yann.morin.1998@free.fr>

Regards,
Yann E. MORIN.

> ---
>  Config.in.legacy               | 32 ++++++++++++++++++++++++++++++++
>  package/ti-sgx-km/Config.in    | 10 +++++-----
>  package/ti-sgx-km/ti-sgx-km.mk |  8 ++++----
>  3 files changed, 41 insertions(+), 9 deletions(-)
> 
> diff --git a/Config.in.legacy b/Config.in.legacy
> index 981306f469..5cf25463ad 100644
> --- a/Config.in.legacy
> +++ b/Config.in.legacy
> @@ -145,6 +145,38 @@ endif
>  ###############################################################################
>  comment "Legacy options removed in 2018.05"
>  
> +config BR2_PACKAGE_TI_SGX_AM335X
> +	bool "ti-sgx-km AM335X option renamed"
> +	select BR2_LEGACY
> +	help
> +	  For consistency reasons, the option
> +	  BR2_PACKAGE_TI_SGX_AM335X has been renamed to
> +	  BR2_PACKAGE_TI_SGX_KM_AM335X.
> +
> +config BR2_PACKAGE_TI_SGX_AM437X
> +	bool "ti-sgx-km AM437X option renamed"
> +	select BR2_LEGACY
> +	help
> +	  For consistency reasons, the option
> +	  BR2_PACKAGE_TI_SGX_AM437X has been renamed to
> +	  BR2_PACKAGE_TI_SGX_KM_AM437X.
> +
> +config BR2_PACKAGE_TI_SGX_AM4430
> +	bool "ti-sgx-km AM4430 option renamed"
> +	select BR2_LEGACY
> +	help
> +	  For consistency reasons, the option
> +	  BR2_PACKAGE_TI_SGX_AM4430 has been renamed to
> +	  BR2_PACKAGE_TI_SGX_KM_AM4430.
> +
> +config BR2_PACKAGE_TI_SGX_AM5430
> +	bool "ti-sgx-km AM5430 option renamed"
> +	select BR2_LEGACY
> +	help
> +	  For consistency reasons, the option
> +	  BR2_PACKAGE_TI_SGX_AM5430 has been renamed to
> +	  BR2_PACKAGE_TI_SGX_KM_AM5430.
> +
>  config BR2_PACKAGE_JANUS_AUDIO_BRIDGE
>  	bool "janus-gateway audio-bridge option renamed"
>  	select BR2_LEGACY
> diff --git a/package/ti-sgx-km/Config.in b/package/ti-sgx-km/Config.in
> index a4c9bb8ca2..db3d3f9ddd 100644
> --- a/package/ti-sgx-km/Config.in
> +++ b/package/ti-sgx-km/Config.in
> @@ -20,26 +20,26 @@ if BR2_PACKAGE_TI_SGX_KM
>  
>  choice
>  	prompt "Target"
> -	default BR2_PACKAGE_TI_SGX_AM335X
> +	default BR2_PACKAGE_TI_SGX_KM_AM335X
>  	help
>  	  Select the SOC for which you would like to install drivers.
>  
> -config BR2_PACKAGE_TI_SGX_AM335X
> +config BR2_PACKAGE_TI_SGX_KM_AM335X
>  	bool "AM335x"
>  	help
>  	  AM335x CPU
>  
> -config BR2_PACKAGE_TI_SGX_AM437X
> +config BR2_PACKAGE_TI_SGX_KM_AM437X
>  	bool "AM437x"
>  	help
>  	  AM437x CPU
>  
> -config BR2_PACKAGE_TI_SGX_AM4430
> +config BR2_PACKAGE_TI_SGX_KM_AM4430
>  	bool "AM4430"
>  	help
>  	  AM4430 CPU
>  
> -config BR2_PACKAGE_TI_SGX_AM5430
> +config BR2_PACKAGE_TI_SGX_KM_AM5430
>  	bool "AM5430"
>  	help
>  	  AM5430 CPU
> diff --git a/package/ti-sgx-km/ti-sgx-km.mk b/package/ti-sgx-km/ti-sgx-km.mk
> index db74da9b4a..0e1bc33902 100644
> --- a/package/ti-sgx-km/ti-sgx-km.mk
> +++ b/package/ti-sgx-km/ti-sgx-km.mk
> @@ -17,13 +17,13 @@ TI_SGX_KM_MAKE_OPTS = \
>  	KERNELDIR=$(LINUX_DIR) \
>  	PVR_NULLDRM=1
>  
> -ifeq ($(BR2_PACKAGE_TI_SGX_AM335X),y)
> +ifeq ($(BR2_PACKAGE_TI_SGX_KM_AM335X),y)
>  TI_SGX_KM_PLATFORM_NAME = omap335x
> -else ifeq ($(BR2_PACKAGE_TI_SGX_AM437X),y)
> +else ifeq ($(BR2_PACKAGE_TI_SGX_KM_AM437X),y)
>  TI_SGX_KM_PLATFORM_NAME = omap437x
> -else ifeq ($(BR2_PACKAGE_TI_SGX_AM4430),y)
> +else ifeq ($(BR2_PACKAGE_TI_SGX_KM_AM4430),y)
>  TI_SGX_KM_PLATFORM_NAME = omap4430
> -else ifeq ($(BR2_PACKAGE_TI_SGX_5430),y)
> +else ifeq ($(BR2_PACKAGE_TI_SGX_KM_5430),y)
>  TI_SGX_KM_PLATFORM_NAME = omap5430
>  endif
>  
> -- 
> 2.14.3
> 
> _______________________________________________
> buildroot mailing list
> buildroot@busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
Arnout Vandecappelle May 15, 2018, 9:52 p.m. | #2
On 13-05-18 21:31, Yann E. MORIN wrote:
> Thomas, All,
> 
> On 2018-05-13 21:07 +0200, Thomas Petazzoni spake thusly:
>> The sub-options of the ti-sgx-km package had their name option
>> prefixed by BR2_PACKAGE_TI_SGX, while the prefix should be
>> BR2_PACKAGE_TI_SGX_KM. This commit fixes that, and adds the necessary
>> Config.in.legacy handling.
>>
>> Since those options are part of a choice, the legacy handling cannot
>> select the new name of the options, so the legacy handling only
>> informs the user of the rename.
> 
> As I was explaining on IRC, we /could/ have legacy handling for choices.
> This would be done in three parts;
> 
>   - the new options replace the old ones in the choice, as we currently
>     do (and as is done in this patch);
> 
>   - this choice is given a "name" (see below), so we can redefine it
>     elsewhere;
> 
>   - in the legacy menu, we duplicate the choice with the same "name"
>     and the same options, but with a set of "default-if" options.
> 
> 
> For example:
> 
>     # In bar/Config.in:
>     choice BAR
>         bool "bar choice"
>     config BAR_1
>         bool "bar 1"
>     config BAR_2
>         bool "bar 2"
>     endchoice
> 
>     # In Config.in.legacy:
>     choice BAR
>         bool "bar choice"
>         default BAR_1 if FOO_1
>         default BAR_2 if FOO_2
>     config BAR_1
>         bool "bar 1"
>     config BAR_2
>         bool "bar 2"
>     endchoice
> 
>     config FOO_1
>         bool "foo 1 was renamed"
>     config FOO_2
>         bool "foo 2 was renamed"
> 
> (not tested, but it should work).

 I tested, it works, but it needlessly repeats the user-visible choice in the
legacy menu. This is simpler and works as well:

# In bar/Config.in:
choice BAR
	bool "bar choice"
config BAR_1
	bool "bar 1"
config BAR_2
	bool "bar 2"
endchoice

# In Config.in.legacy:
choice BAR
	default BAR_1 if FOO_1
	default BAR_2 if FOO_2
endchoice

config FOO_1
	bool "foo 1 was renamed"
config FOO_2
	bool "foo 2 was renamed"


> What is nice with this solution, is that we have the new choice that is
> right near the legacy option so we can chek it, and it automatically
> gets the old setting.
> 
> But I am not too convinced, however, because we do not usually use the
> name of a choice elsewhere...

 Legacy is pretty special anyway. I do think it's worthwhile it to do this properly.

 Regards,
 Arnout

> 
>> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
> 
> Acked-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
> 
> Regards,
> Yann E. MORIN.
> 
>> ---
>>  Config.in.legacy               | 32 ++++++++++++++++++++++++++++++++
>>  package/ti-sgx-km/Config.in    | 10 +++++-----
>>  package/ti-sgx-km/ti-sgx-km.mk |  8 ++++----
>>  3 files changed, 41 insertions(+), 9 deletions(-)
>>
>> diff --git a/Config.in.legacy b/Config.in.legacy
>> index 981306f469..5cf25463ad 100644
>> --- a/Config.in.legacy
>> +++ b/Config.in.legacy
>> @@ -145,6 +145,38 @@ endif
>>  ###############################################################################
>>  comment "Legacy options removed in 2018.05"
>>  
>> +config BR2_PACKAGE_TI_SGX_AM335X
>> +	bool "ti-sgx-km AM335X option renamed"
>> +	select BR2_LEGACY
>> +	help
>> +	  For consistency reasons, the option
>> +	  BR2_PACKAGE_TI_SGX_AM335X has been renamed to
>> +	  BR2_PACKAGE_TI_SGX_KM_AM335X.
>> +
>> +config BR2_PACKAGE_TI_SGX_AM437X
>> +	bool "ti-sgx-km AM437X option renamed"
>> +	select BR2_LEGACY
>> +	help
>> +	  For consistency reasons, the option
>> +	  BR2_PACKAGE_TI_SGX_AM437X has been renamed to
>> +	  BR2_PACKAGE_TI_SGX_KM_AM437X.
>> +
>> +config BR2_PACKAGE_TI_SGX_AM4430
>> +	bool "ti-sgx-km AM4430 option renamed"
>> +	select BR2_LEGACY
>> +	help
>> +	  For consistency reasons, the option
>> +	  BR2_PACKAGE_TI_SGX_AM4430 has been renamed to
>> +	  BR2_PACKAGE_TI_SGX_KM_AM4430.
>> +
>> +config BR2_PACKAGE_TI_SGX_AM5430
>> +	bool "ti-sgx-km AM5430 option renamed"
>> +	select BR2_LEGACY
>> +	help
>> +	  For consistency reasons, the option
>> +	  BR2_PACKAGE_TI_SGX_AM5430 has been renamed to
>> +	  BR2_PACKAGE_TI_SGX_KM_AM5430.
>> +
>>  config BR2_PACKAGE_JANUS_AUDIO_BRIDGE
>>  	bool "janus-gateway audio-bridge option renamed"
>>  	select BR2_LEGACY
>> diff --git a/package/ti-sgx-km/Config.in b/package/ti-sgx-km/Config.in
>> index a4c9bb8ca2..db3d3f9ddd 100644
>> --- a/package/ti-sgx-km/Config.in
>> +++ b/package/ti-sgx-km/Config.in
>> @@ -20,26 +20,26 @@ if BR2_PACKAGE_TI_SGX_KM
>>  
>>  choice
>>  	prompt "Target"
>> -	default BR2_PACKAGE_TI_SGX_AM335X
>> +	default BR2_PACKAGE_TI_SGX_KM_AM335X
>>  	help
>>  	  Select the SOC for which you would like to install drivers.
>>  
>> -config BR2_PACKAGE_TI_SGX_AM335X
>> +config BR2_PACKAGE_TI_SGX_KM_AM335X
>>  	bool "AM335x"
>>  	help
>>  	  AM335x CPU
>>  
>> -config BR2_PACKAGE_TI_SGX_AM437X
>> +config BR2_PACKAGE_TI_SGX_KM_AM437X
>>  	bool "AM437x"
>>  	help
>>  	  AM437x CPU
>>  
>> -config BR2_PACKAGE_TI_SGX_AM4430
>> +config BR2_PACKAGE_TI_SGX_KM_AM4430
>>  	bool "AM4430"
>>  	help
>>  	  AM4430 CPU
>>  
>> -config BR2_PACKAGE_TI_SGX_AM5430
>> +config BR2_PACKAGE_TI_SGX_KM_AM5430
>>  	bool "AM5430"
>>  	help
>>  	  AM5430 CPU
>> diff --git a/package/ti-sgx-km/ti-sgx-km.mk b/package/ti-sgx-km/ti-sgx-km.mk
>> index db74da9b4a..0e1bc33902 100644
>> --- a/package/ti-sgx-km/ti-sgx-km.mk
>> +++ b/package/ti-sgx-km/ti-sgx-km.mk
>> @@ -17,13 +17,13 @@ TI_SGX_KM_MAKE_OPTS = \
>>  	KERNELDIR=$(LINUX_DIR) \
>>  	PVR_NULLDRM=1
>>  
>> -ifeq ($(BR2_PACKAGE_TI_SGX_AM335X),y)
>> +ifeq ($(BR2_PACKAGE_TI_SGX_KM_AM335X),y)
>>  TI_SGX_KM_PLATFORM_NAME = omap335x
>> -else ifeq ($(BR2_PACKAGE_TI_SGX_AM437X),y)
>> +else ifeq ($(BR2_PACKAGE_TI_SGX_KM_AM437X),y)
>>  TI_SGX_KM_PLATFORM_NAME = omap437x
>> -else ifeq ($(BR2_PACKAGE_TI_SGX_AM4430),y)
>> +else ifeq ($(BR2_PACKAGE_TI_SGX_KM_AM4430),y)
>>  TI_SGX_KM_PLATFORM_NAME = omap4430
>> -else ifeq ($(BR2_PACKAGE_TI_SGX_5430),y)
>> +else ifeq ($(BR2_PACKAGE_TI_SGX_KM_5430),y)
>>  TI_SGX_KM_PLATFORM_NAME = omap5430
>>  endif
>>  
>> -- 
>> 2.14.3
>>
>> _______________________________________________
>> buildroot mailing list
>> buildroot@busybox.net
>> http://lists.busybox.net/mailman/listinfo/buildroot
>
Thomas Petazzoni May 16, 2018, 7 a.m. | #3
Hello,

On Tue, 15 May 2018 23:52:33 +0200, Arnout Vandecappelle wrote:

> > What is nice with this solution, is that we have the new choice that is
> > right near the legacy option so we can chek it, and it automatically
> > gets the old setting.
> > 
> > But I am not too convinced, however, because we do not usually use the
> > name of a choice elsewhere...  
> 
>  Legacy is pretty special anyway. I do think it's worthwhile it to do this properly.

Is this an Acked-by to the approach this patch series has taken in
terms of handling the Config.in choice option renaming ?

Thanks! :-)

Thomas
Arnout Vandecappelle May 16, 2018, 3:16 p.m. | #4
On 16-05-18 09:00, Thomas Petazzoni wrote:
> Hello,
> 
> On Tue, 15 May 2018 23:52:33 +0200, Arnout Vandecappelle wrote:
> 
>>> What is nice with this solution, is that we have the new choice that is
>>> right near the legacy option so we can chek it, and it automatically
>>> gets the old setting.
>>>
>>> But I am not too convinced, however, because we do not usually use the
>>> name of a choice elsewhere...  
>>
>>  Legacy is pretty special anyway. I do think it's worthwhile it to do this properly.
> 
> Is this an Acked-by to the approach this patch series has taken in
> terms of handling the Config.in choice option renaming ?

 Er, no, it's a NACK. I *do* think it's worthwhile to properly select the new
option.

 Regards,
 Arnout

> 
> Thanks! :-)
> 
> Thomas
>
Peter Korsgaard May 21, 2018, 9:16 p.m. | #5
>>>>> "Arnout" == Arnout Vandecappelle <arnout@mind.be> writes:

 > On 16-05-18 09:00, Thomas Petazzoni wrote:
 >> Hello,
 >> 
 >> On Tue, 15 May 2018 23:52:33 +0200, Arnout Vandecappelle wrote:
 >> 
 >>>> What is nice with this solution, is that we have the new choice that is
 >>>> right near the legacy option so we can chek it, and it automatically
 >>>> gets the old setting.
 >>>> 
 >>>> But I am not too convinced, however, because we do not usually use the
 >>>> name of a choice elsewhere...  
 >>> 
 >>> Legacy is pretty special anyway. I do think it's worthwhile it to do this properly.
 >> 
 >> Is this an Acked-by to the approach this patch series has taken in
 >> terms of handling the Config.in choice option renaming ?

 >  Er, no, it's a NACK. I *do* think it's worthwhile to properly select the new
 > option.

OK. I would like to release RC2 and include these renames, so how about
you send a followup series with the reworked Config.in.legacy handling?

Thanks.
Arnout Vandecappelle May 22, 2018, 10:42 a.m. | #6
On 21-05-18 23:16, Peter Korsgaard wrote:
>>>>>> "Arnout" == Arnout Vandecappelle <arnout@mind.be> writes:
> 
>  > On 16-05-18 09:00, Thomas Petazzoni wrote:
>  >> Hello,
>  >> 
>  >> On Tue, 15 May 2018 23:52:33 +0200, Arnout Vandecappelle wrote:
>  >> 
>  >>>> What is nice with this solution, is that we have the new choice that is
>  >>>> right near the legacy option so we can chek it, and it automatically
>  >>>> gets the old setting.
>  >>>> 
>  >>>> But I am not too convinced, however, because we do not usually use the
>  >>>> name of a choice elsewhere...  
>  >>> 
>  >>> Legacy is pretty special anyway. I do think it's worthwhile it to do this properly.
>  >> 
>  >> Is this an Acked-by to the approach this patch series has taken in
>  >> terms of handling the Config.in choice option renaming ?
> 
>  >  Er, no, it's a NACK. I *do* think it's worthwhile to properly select the new
>  > option.
> 
> OK. I would like to release RC2 and include these renames, so how about
> you send a followup series with the reworked Config.in.legacy handling?

 At the pace that I've been active in Buildroot lately, not likely, but I'll
give it a shot :-)

 Regards,
 Arnout
Yann E. MORIN May 28, 2018, 8:45 p.m. | #7
Arnout, Peter, All,

On 2018-05-22 12:42 +0200, Arnout Vandecappelle spake thusly:
> On 21-05-18 23:16, Peter Korsgaard wrote:
> >>>>>> "Arnout" == Arnout Vandecappelle <arnout@mind.be> writes:
> > 
> >  > On 16-05-18 09:00, Thomas Petazzoni wrote:
> >  >> Hello,
> >  >> 
> >  >> On Tue, 15 May 2018 23:52:33 +0200, Arnout Vandecappelle wrote:
> >  >> 
> >  >>>> What is nice with this solution, is that we have the new choice that is
> >  >>>> right near the legacy option so we can chek it, and it automatically
> >  >>>> gets the old setting.
> >  >>>> 
> >  >>>> But I am not too convinced, however, because we do not usually use the
> >  >>>> name of a choice elsewhere...  
> >  >>> 
> >  >>> Legacy is pretty special anyway. I do think it's worthwhile it to do this properly.
> >  >>
> >  >> Is this an Acked-by to the approach this patch series has taken in
> >  >> terms of handling the Config.in choice option renaming ?
> > 
> >  >  Er, no, it's a NACK. I *do* think it's worthwhile to properly select the new
> >  > option.

Yeah, but as we've gone without support for legacy choices so far
(almost 6 years now), I don't think this is an urgent matter.

Next time, maybe I'll just shut up instead of suggesting sophisticated
and imaginative solutions. ;-P

Regards,
Yann E. MORIN.
Arnout Vandecappelle May 29, 2018, 10:45 a.m. | #8
On 28-05-18 22:45, Yann E. MORIN wrote:
> Arnout, Peter, All,
> 
> On 2018-05-22 12:42 +0200, Arnout Vandecappelle spake thusly:
>> On 21-05-18 23:16, Peter Korsgaard wrote:
>>>>>>>> "Arnout" == Arnout Vandecappelle <arnout@mind.be> writes:
>>>
>>>  > On 16-05-18 09:00, Thomas Petazzoni wrote:
>>>  >> Hello,
>>>  >> 
>>>  >> On Tue, 15 May 2018 23:52:33 +0200, Arnout Vandecappelle wrote:
>>>  >> 
>>>  >>>> What is nice with this solution, is that we have the new choice that is
>>>  >>>> right near the legacy option so we can chek it, and it automatically
>>>  >>>> gets the old setting.
>>>  >>>> 
>>>  >>>> But I am not too convinced, however, because we do not usually use the
>>>  >>>> name of a choice elsewhere...  
>>>  >>> 
>>>  >>> Legacy is pretty special anyway. I do think it's worthwhile it to do this properly.
>>>  >>
>>>  >> Is this an Acked-by to the approach this patch series has taken in
>>>  >> terms of handling the Config.in choice option renaming ?
>>>
>>>  >  Er, no, it's a NACK. I *do* think it's worthwhile to properly select the new
>>>  > option.
> 
> Yeah, but as we've gone without support for legacy choices so far
> (almost 6 years now), I don't think this is an urgent matter.

 Excuse me? Have you read lines 19-59 of Config.in.legacy?

 Regards,
 Arnout

> 
> Next time, maybe I'll just shut up instead of suggesting sophisticated
> and imaginative solutions. ;-P
> 
> Regards,
> Yann E. MORIN.
>
Yann E. MORIN May 29, 2018, 5:26 p.m. | #9
Arnout, All,

On 2018-05-29 12:45 +0200, Arnout Vandecappelle spake thusly:
> On 28-05-18 22:45, Yann E. MORIN wrote:
> > Arnout, Peter, All,
> > 
> > On 2018-05-22 12:42 +0200, Arnout Vandecappelle spake thusly:
> >> On 21-05-18 23:16, Peter Korsgaard wrote:
> >>>>>>>> "Arnout" == Arnout Vandecappelle <arnout@mind.be> writes:
> >>>
> >>>  > On 16-05-18 09:00, Thomas Petazzoni wrote:
> >>>  >> Hello,
> >>>  >> 
> >>>  >> On Tue, 15 May 2018 23:52:33 +0200, Arnout Vandecappelle wrote:
> >>>  >> 
> >>>  >>>> What is nice with this solution, is that we have the new choice that is
> >>>  >>>> right near the legacy option so we can chek it, and it automatically
> >>>  >>>> gets the old setting.
> >>>  >>>> 
> >>>  >>>> But I am not too convinced, however, because we do not usually use the
> >>>  >>>> name of a choice elsewhere...  
> >>>  >>> 
> >>>  >>> Legacy is pretty special anyway. I do think it's worthwhile it to do this properly.
> >>>  >>
> >>>  >> Is this an Acked-by to the approach this patch series has taken in
> >>>  >> terms of handling the Config.in choice option renaming ?
> >>>
> >>>  >  Er, no, it's a NACK. I *do* think it's worthwhile to properly select the new
> >>>  > option.
> > 
> > Yeah, but as we've gone without support for legacy choices so far
> > (almost 6 years now), I don't think this is an urgent matter.
> 
>  Excuse me? Have you read lines 19-59 of Config.in.legacy?

Sorry, but this is not about "legacy choices" as I suggested above by
using named choices. This is about how to handle options in a choice, by
moving them to Config.in.legacy as plain booleans.

Now, to be clear:

  - yes, we do want to have proper legacy handling for the renamed
    options, as is done in commit b54c5464cc, where the old choice
    entries have been added to legacy, according to the documentation
    we had at that time and following existing practice, but which
    "forgot" the defaults for legacy [0];

  - no we don't need to have support for adding /legacy choices/ (i.e.
    using a named choice) for the 2018.05 release because it is new and
    we have so far never handled legacy choice options in a /legacy
    choice/.


[0] Fixed with this patch, which I'll submit in a moment:
    diff --git a/package/ti-sgx-km/Config.in b/package/ti-sgx-km/Config.in
    index db3d3f9ddd..562bbe8867 100644
    --- a/package/ti-sgx-km/Config.in
    +++ b/package/ti-sgx-km/Config.in
    @@ -20,6 +20,10 @@ if BR2_PACKAGE_TI_SGX_KM
     
     choice
     	prompt "Target"
    +	default BR2_PACKAGE_TI_SGX_KM_AM335X if BR2_PACKAGE_TI_SGX_AM335X # legacy
    +	default BR2_PACKAGE_TI_SGX_KM_AM437X if BR2_PACKAGE_TI_SGX_AM437X # legacy
    +	default BR2_PACKAGE_TI_SGX_KM_AM4430 if BR2_PACKAGE_TI_SGX_AM4430 # legacy
    +	default BR2_PACKAGE_TI_SGX_KM_AM5430 if BR2_PACKAGE_TI_SGX_AM5430 # legacy
     	default BR2_PACKAGE_TI_SGX_KM_AM335X
     	help
     	  Select the SOC for which you would like to install drivers.

BTW, the fallback default here is about the first option in the choice,
so it is not needed, but oh well... :-/

Regards,
Yann E. MORIN.

>  Regards,
>  Arnout
> 
> > 
> > Next time, maybe I'll just shut up instead of suggesting sophisticated
> > and imaginative solutions. ;-P
> > 
> > Regards,
> > Yann E. MORIN.
> > 
> 
> -- 
> Arnout Vandecappelle                          arnout at mind be
> Senior Embedded Software Architect            +32-16-286500
> Essensium/Mind                                http://www.mind.be
> G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
> LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
> GPG fingerprint:  7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF

Patch

diff --git a/Config.in.legacy b/Config.in.legacy
index 981306f469..5cf25463ad 100644
--- a/Config.in.legacy
+++ b/Config.in.legacy
@@ -145,6 +145,38 @@  endif
 ###############################################################################
 comment "Legacy options removed in 2018.05"
 
+config BR2_PACKAGE_TI_SGX_AM335X
+	bool "ti-sgx-km AM335X option renamed"
+	select BR2_LEGACY
+	help
+	  For consistency reasons, the option
+	  BR2_PACKAGE_TI_SGX_AM335X has been renamed to
+	  BR2_PACKAGE_TI_SGX_KM_AM335X.
+
+config BR2_PACKAGE_TI_SGX_AM437X
+	bool "ti-sgx-km AM437X option renamed"
+	select BR2_LEGACY
+	help
+	  For consistency reasons, the option
+	  BR2_PACKAGE_TI_SGX_AM437X has been renamed to
+	  BR2_PACKAGE_TI_SGX_KM_AM437X.
+
+config BR2_PACKAGE_TI_SGX_AM4430
+	bool "ti-sgx-km AM4430 option renamed"
+	select BR2_LEGACY
+	help
+	  For consistency reasons, the option
+	  BR2_PACKAGE_TI_SGX_AM4430 has been renamed to
+	  BR2_PACKAGE_TI_SGX_KM_AM4430.
+
+config BR2_PACKAGE_TI_SGX_AM5430
+	bool "ti-sgx-km AM5430 option renamed"
+	select BR2_LEGACY
+	help
+	  For consistency reasons, the option
+	  BR2_PACKAGE_TI_SGX_AM5430 has been renamed to
+	  BR2_PACKAGE_TI_SGX_KM_AM5430.
+
 config BR2_PACKAGE_JANUS_AUDIO_BRIDGE
 	bool "janus-gateway audio-bridge option renamed"
 	select BR2_LEGACY
diff --git a/package/ti-sgx-km/Config.in b/package/ti-sgx-km/Config.in
index a4c9bb8ca2..db3d3f9ddd 100644
--- a/package/ti-sgx-km/Config.in
+++ b/package/ti-sgx-km/Config.in
@@ -20,26 +20,26 @@  if BR2_PACKAGE_TI_SGX_KM
 
 choice
 	prompt "Target"
-	default BR2_PACKAGE_TI_SGX_AM335X
+	default BR2_PACKAGE_TI_SGX_KM_AM335X
 	help
 	  Select the SOC for which you would like to install drivers.
 
-config BR2_PACKAGE_TI_SGX_AM335X
+config BR2_PACKAGE_TI_SGX_KM_AM335X
 	bool "AM335x"
 	help
 	  AM335x CPU
 
-config BR2_PACKAGE_TI_SGX_AM437X
+config BR2_PACKAGE_TI_SGX_KM_AM437X
 	bool "AM437x"
 	help
 	  AM437x CPU
 
-config BR2_PACKAGE_TI_SGX_AM4430
+config BR2_PACKAGE_TI_SGX_KM_AM4430
 	bool "AM4430"
 	help
 	  AM4430 CPU
 
-config BR2_PACKAGE_TI_SGX_AM5430
+config BR2_PACKAGE_TI_SGX_KM_AM5430
 	bool "AM5430"
 	help
 	  AM5430 CPU
diff --git a/package/ti-sgx-km/ti-sgx-km.mk b/package/ti-sgx-km/ti-sgx-km.mk
index db74da9b4a..0e1bc33902 100644
--- a/package/ti-sgx-km/ti-sgx-km.mk
+++ b/package/ti-sgx-km/ti-sgx-km.mk
@@ -17,13 +17,13 @@  TI_SGX_KM_MAKE_OPTS = \
 	KERNELDIR=$(LINUX_DIR) \
 	PVR_NULLDRM=1
 
-ifeq ($(BR2_PACKAGE_TI_SGX_AM335X),y)
+ifeq ($(BR2_PACKAGE_TI_SGX_KM_AM335X),y)
 TI_SGX_KM_PLATFORM_NAME = omap335x
-else ifeq ($(BR2_PACKAGE_TI_SGX_AM437X),y)
+else ifeq ($(BR2_PACKAGE_TI_SGX_KM_AM437X),y)
 TI_SGX_KM_PLATFORM_NAME = omap437x
-else ifeq ($(BR2_PACKAGE_TI_SGX_AM4430),y)
+else ifeq ($(BR2_PACKAGE_TI_SGX_KM_AM4430),y)
 TI_SGX_KM_PLATFORM_NAME = omap4430
-else ifeq ($(BR2_PACKAGE_TI_SGX_5430),y)
+else ifeq ($(BR2_PACKAGE_TI_SGX_KM_5430),y)
 TI_SGX_KM_PLATFORM_NAME = omap5430
 endif