2017-09-08 16:39:48

by Stephen Hemminger

[permalink] [raw]
Subject: [PATCH] media: default for RC_CORE should be n

The Linus policy on Kconfig is that the default should be no
for all new devices. I.e the user rebuild a new kernel from an
old config should not by default get a larger kernel.

Fixes: b4c184e506a4 ("[media] media: reorganize the main Kconfig items")
Signed-off-by: Stephen Hemminger <[email protected]>
---
drivers/media/rc/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/media/rc/Kconfig b/drivers/media/rc/Kconfig
index d9ce8ff55d0c..5aa384afcfef 100644
--- a/drivers/media/rc/Kconfig
+++ b/drivers/media/rc/Kconfig
@@ -2,7 +2,7 @@
menuconfig RC_CORE
tristate "Remote Controller support"
depends on INPUT
- default y
+ default n
---help---
Enable support for Remote Controllers on Linux. This is
needed in order to support several video capture adapters,
--
2.11.0


2017-09-08 18:52:51

by Sean Young

[permalink] [raw]
Subject: Re: [PATCH] media: default for RC_CORE should be n

On Fri, Sep 08, 2017 at 09:39:29AM -0700, Stephen Hemminger wrote:
> The Linus policy on Kconfig is that the default should be no
> for all new devices. I.e the user rebuild a new kernel from an
> old config should not by default get a larger kernel.

That might make sense for new config, but RC_CORE has been present for
7 years; I don't see how changing defaults for existing config makes
sense.


Sean

>
> Fixes: b4c184e506a4 ("[media] media: reorganize the main Kconfig items")
> Signed-off-by: Stephen Hemminger <[email protected]>
> ---
> drivers/media/rc/Kconfig | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/media/rc/Kconfig b/drivers/media/rc/Kconfig
> index d9ce8ff55d0c..5aa384afcfef 100644
> --- a/drivers/media/rc/Kconfig
> +++ b/drivers/media/rc/Kconfig
> @@ -2,7 +2,7 @@
> menuconfig RC_CORE
> tristate "Remote Controller support"
> depends on INPUT
> - default y
> + default n
> ---help---
> Enable support for Remote Controllers on Linux. This is
> needed in order to support several video capture adapters,
> --
> 2.11.0

2017-09-08 19:07:00

by Stephen Hemminger

[permalink] [raw]
Subject: Re: [PATCH] media: default for RC_CORE should be n

On Fri, 8 Sep 2017 19:52:47 +0100
Sean Young <[email protected]> wrote:

> On Fri, Sep 08, 2017 at 09:39:29AM -0700, Stephen Hemminger wrote:
> > The Linus policy on Kconfig is that the default should be no
> > for all new devices. I.e the user rebuild a new kernel from an
> > old config should not by default get a larger kernel.
>
> That might make sense for new config, but RC_CORE has been present for
> 7 years; I don't see how changing defaults for existing config makes
> sense.
>

I took existing config for 4.13 and did 'make oldconfig' and just
hitting return caused it to turned on.

The problem is that in my config media is disabled, and now your new
reconfiguration makes RC_CORE not dependent on media.

It is a common problem, developers never test with their subsystem disabled.


Attachments:
(No filename) (796.00 B)
config-linux-next (95.99 kB)
Download all attachments

2017-09-08 21:52:09

by Mauro Carvalho Chehab

[permalink] [raw]
Subject: Re: [PATCH] media: default for RC_CORE should be n

Em Fri, 8 Sep 2017 12:06:48 -0700
Stephen Hemminger <[email protected]> escreveu:

> On Fri, 8 Sep 2017 19:52:47 +0100
> Sean Young <[email protected]> wrote:
>
> > On Fri, Sep 08, 2017 at 09:39:29AM -0700, Stephen Hemminger wrote:
> > > The Linus policy on Kconfig is that the default should be no
> > > for all new devices. I.e the user rebuild a new kernel from an
> > > old config should not by default get a larger kernel.
> >
> > That might make sense for new config, but RC_CORE has been present for
> > 7 years; I don't see how changing defaults for existing config makes
> > sense.
> >
>
> I took existing config for 4.13 and did 'make oldconfig' and just
> hitting return caused it to turned on.
>
> The problem is that in my config media is disabled, and now your new
> reconfiguration makes RC_CORE not dependent on media.
>
> It is a common problem, developers never test with their subsystem disabled.

Hi Sean,

Yes, it makes sense to default 'n' for RC_CORE now that this is an
independent menu option and it builds the RC core when enabled.

Regards,
Mauro

2017-09-19 12:25:31

by Geert Uytterhoeven

[permalink] [raw]
Subject: Re: [PATCH] media: default for RC_CORE should be n

On Fri, Sep 8, 2017 at 6:39 PM, Stephen Hemminger
<[email protected]> wrote:
> The Linus policy on Kconfig is that the default should be no
> for all new devices. I.e the user rebuild a new kernel from an
> old config should not by default get a larger kernel.
>
> Fixes: b4c184e506a4 ("[media] media: reorganize the main Kconfig items")
> Signed-off-by: Stephen Hemminger <[email protected]>
> ---
> drivers/media/rc/Kconfig | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/media/rc/Kconfig b/drivers/media/rc/Kconfig
> index d9ce8ff55d0c..5aa384afcfef 100644
> --- a/drivers/media/rc/Kconfig
> +++ b/drivers/media/rc/Kconfig
> @@ -2,7 +2,7 @@
> menuconfig RC_CORE
> tristate "Remote Controller support"
> depends on INPUT
> - default y
> + default n

"default n" is the default, so you can just drop this line.

For the principle:
Acked-by: Geert Uytterhoeven <[email protected]>

Gr{oetje,eeting}s,

Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [email protected]

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds