On Sat, Sep 26, 2020 at 09:42:40PM +0200, Michał Mirosław wrote:
Make tegra20-spdif default to N as all other drivers do.
Signed-off-by: Michał Mirosław mirq-linux@rere.qmqm.pl Fixes: 774fec338bfc ("ASoC: Tegra: Implement SPDIF CPU DAI")
I don't think this is warranted. This doesn't fix a bug or anything. It's merely a change in the default configuration. The presence of a Fixes: tag is typically used as a hint for people to pick this up into stable releases, but I don't think this qualifies.
sound/soc/tegra/Kconfig | 1 - 1 file changed, 1 deletion(-)
diff --git a/sound/soc/tegra/Kconfig b/sound/soc/tegra/Kconfig index 3d91bd3e59cd..a62cc87551ac 100644 --- a/sound/soc/tegra/Kconfig +++ b/sound/soc/tegra/Kconfig @@ -39,7 +39,6 @@ config SND_SOC_TEGRA20_I2S config SND_SOC_TEGRA20_SPDIF tristate "Tegra20 SPDIF interface" depends on SND_SOC_TEGRA
- default m help Say Y or M if you want to add support for the Tegra20 SPDIF interface. You will also need to select the individual machine drivers to support
So now by default this driver will be disabled, which means that Linux is going to regress for people that rely on this driver.
You need to at least follow this up with a patch that makes the corresponding change in both tegra_defconfig and multi_v7_defconfig to ensure that this driver is going to get built by default.
Given the above it's probably also a good idea to explain a bit more in the commit message about what you're trying to achieve. Yes, "default n" is usually the right thing to do and I'm honestly not sure why Stephen chose to make this "default m" back in the day. Given that it depends on SND_SOC_TEGRA, which itself is "default n", I think this makes some sense, even if in retrospect it ended up being a bit inconsistent (you could probably argue that all patches after this are the ones that were inconsistent instead). This was merged over 9 years ago and a lot of common practices have changed over that period of time.
Thierry