[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <341b9177-180c-8fc1-f9cc-27f3b48a8b9c@gmail.com>
Date: Wed, 24 Jul 2019 14:29:30 +0300
From: Dmitry Osipenko <digetx@...il.com>
To: Jon Hunter <jonathanh@...dia.com>,
Viswanath L <viswanathl@...dia.com>, thierry.reding@...il.com
Cc: airlied@...ux.ie, daniel@...ll.ch, dri-devel@...ts.freedesktop.org,
linux-tegra@...r.kernel.org, linux-kernel@...r.kernel.org,
stable@...r.kernel.org
Subject: Re: [PATCH v3] drm/tegra: sor: Enable HDA interrupts at plug-in
24.07.2019 14:11, Jon Hunter пишет:
>
> On 24/07/2019 10:27, Dmitry Osipenko wrote:
>> 23.07.2019 15:40, Viswanath L пишет:
>>> HDMI plugout calls runtime suspend, which clears interrupt registers
>>> and causes audio functionality to break on subsequent plug-in; setting
>>> interrupt registers in sor_audio_prepare() solves the issue.
>>>
>>> Signed-off-by: Viswanath L <viswanathl@...dia.com>
>>
>> Yours signed-off-by always should be the last line of the commit's
>> message because the text below it belongs to a person who applies this
>> patch, Thierry in this case. This is not a big deal at all and Thierry
>> could make a fixup while applying the patch if will deem that as necessary.
>>
>> Secondly, there is no need to add "stable@...r.kernel.org" to the
>> email's recipients because the patch will flow into stable kernel
>> versions from the mainline once it will get applied. That happens based
>> on the stable tag presence, hence it's enough to add the 'Cc' tag to the
>> commit's message in order to get patch backported.
>
> I believe 'git send-email' automatically does this.
Indeed, completely forgot that I have '--suppress-cc=all' in my git's setup.
Powered by blists - more mailing lists