diff mbox

[5/5] ASoC: omap: Remove OMAP_MUX dependency from Nokia N810 audio support

Message ID 20180426115115.13744-6-peter.ujfalusi@ti.com (mailing list archive)
State New, archived
Headers show

Commit Message

Peter Ujfalusi April 26, 2018, 11:51 a.m. UTC
From: Jarkko Nikula <jarkko.nikula@bitmer.com>

Commit e9f5f1e45608 ("ARM: OMAP2+: Remove legacy mux code") removed
CONFIG_OMAP_MUX making impossible to build Nokia N810 audio support. Remove
this dependency so we can do at least build tests.

Fixes: e9f5f1e45608 ("ARM: OMAP2+: Remove legacy mux code")
Signed-off-by: Jarkko Nikula <jarkko.nikula@bitmer.com>
---
 sound/soc/omap/Kconfig | 1 -
 1 file changed, 1 deletion(-)

Comments

Mark Brown April 26, 2018, 12:54 p.m. UTC | #1
On Thu, Apr 26, 2018 at 02:51:15PM +0300, Peter Ujfalusi wrote:
> From: Jarkko Nikula <jarkko.nikula@bitmer.com>
> 
> Commit e9f5f1e45608 ("ARM: OMAP2+: Remove legacy mux code") removed
> CONFIG_OMAP_MUX making impossible to build Nokia N810 audio support. Remove
> this dependency so we can do at least build tests.
> 
> Fixes: e9f5f1e45608 ("ARM: OMAP2+: Remove legacy mux code")
> Signed-off-by: Jarkko Nikula <jarkko.nikula@bitmer.com>
> ---

You're missing your signoff here.
Peter Ujfalusi April 26, 2018, 1:01 p.m. UTC | #2
Mark,

On 2018-04-26 15:54, Mark Brown wrote:
> On Thu, Apr 26, 2018 at 02:51:15PM +0300, Peter Ujfalusi wrote:
>> From: Jarkko Nikula <jarkko.nikula@bitmer.com>
>>
>> Commit e9f5f1e45608 ("ARM: OMAP2+: Remove legacy mux code") removed
>> CONFIG_OMAP_MUX making impossible to build Nokia N810 audio support. Remove
>> this dependency so we can do at least build tests.
>>
>> Fixes: e9f5f1e45608 ("ARM: OMAP2+: Remove legacy mux code")
>> Signed-off-by: Jarkko Nikula <jarkko.nikula@bitmer.com>
>> ---
> 
> You're missing your signoff here.

I have not changed the patch itself, just picked it from the list to
include to the series. Afaik in this case my signoff is not needed.

Can you add my (or I can resend the series):
Signed-off-by: Peter Ujfalusi <peter.ujfalusi@ti.com>
or
Reviewed-by: Peter Ujfalusi <peter.ujfalusi@ti.com>
or
Acked-by: Peter Ujfalusi <peter.ujfalusi@ti.com>

- Péter

Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki.
Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Mark Brown April 26, 2018, 1:03 p.m. UTC | #3
On Thu, Apr 26, 2018 at 04:01:51PM +0300, Peter Ujfalusi wrote:
> On 2018-04-26 15:54, Mark Brown wrote:

> > You're missing your signoff here.

> I have not changed the patch itself, just picked it from the list to
> include to the series. Afaik in this case my signoff is not needed.

No, you need to add your signoff for *anything* you're submitting.  It's
about tracking the path the patch takes to mainline.

> Can you add my (or I can resend the series):
> Signed-off-by: Peter Ujfalusi <peter.ujfalusi@ti.com>

OK.
Peter Ujfalusi April 26, 2018, 1:06 p.m. UTC | #4
On 2018-04-26 16:03, Mark Brown wrote:
> On Thu, Apr 26, 2018 at 04:01:51PM +0300, Peter Ujfalusi wrote:
>> On 2018-04-26 15:54, Mark Brown wrote:
> 
>>> You're missing your signoff here.
> 
>> I have not changed the patch itself, just picked it from the list to
>> include to the series. Afaik in this case my signoff is not needed.
> 
> No, you need to add your signoff for *anything* you're submitting.  It's
> about tracking the path the patch takes to mainline.

OK. I left it off because recently there were replies from other
maintainers saying otherwise (no need to singoff of unmodified patches
from others).
I agree that adding the signoff is the correct way.

>> Can you add my (or I can resend the series):
>> Signed-off-by: Peter Ujfalusi <peter.ujfalusi@ti.com>
> 
> OK.

Thank you,

- Péter

Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki.
Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Mark Brown April 26, 2018, 1:08 p.m. UTC | #5
On Thu, Apr 26, 2018 at 04:06:51PM +0300, Peter Ujfalusi wrote:
> On 2018-04-26 16:03, Mark Brown wrote:

> > No, you need to add your signoff for *anything* you're submitting.  It's
> > about tracking the path the patch takes to mainline.

> OK. I left it off because recently there were replies from other
> maintainers saying otherwise (no need to singoff of unmodified patches
> from others).
> I agree that adding the signoff is the correct way.

Oh dear, who was saying that - might cause lawyers to get upset...
diff mbox

Patch

diff --git a/sound/soc/omap/Kconfig b/sound/soc/omap/Kconfig
index ba56d71c3ca7..65864a60d0e2 100644
--- a/sound/soc/omap/Kconfig
+++ b/sound/soc/omap/Kconfig
@@ -42,7 +42,6 @@  config SND_OMAP_SOC_HDMI_AUDIO
 config SND_OMAP_SOC_N810
 	tristate "SoC Audio support for Nokia N810"
 	depends on SND_OMAP_SOC && MACH_NOKIA_N810 && I2C
-	depends on OMAP_MUX
 	select SND_OMAP_SOC_MCBSP
 	select SND_SOC_TLV320AIC3X
 	help