All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sowjanya Komatineni <skomatineni@nvidia.com>
To: Greg KH <greg@kroah.com>
Cc: <stable@vger.kernel.org>
Subject: Re: [PATCH v3 09/15] ASoC: tegra: Add fallback for audio mclk
Date: Fri, 6 Dec 2019 09:11:33 -0800	[thread overview]
Message-ID: <febf1f1a-6cca-c4d1-e220-50af5ef13ff7@nvidia.com> (raw)
In-Reply-To: <20191206162934.GA86904@kroah.com>


On 12/6/19 8:29 AM, Greg KH wrote:
> On Fri, Dec 06, 2019 at 08:19:26AM -0800, Sowjanya Komatineni wrote:
>> On 12/5/19 11:09 PM, Greg KH wrote:
>>> On Thu, Dec 05, 2019 at 06:47:12PM -0800, Sowjanya Komatineni wrote:
>>>> mclk is from clk_out_1 which is part of Tegra PMC block and pmc clocks
>>>> are moved to Tegra PMC driver with pmc as clock provider and using pmc
>>>> clock ids.
>>>>
>>>> New device tree uses clk_out_1 from pmc clock provider.
>>>>
>>>> So, this patch adds fallback to extern1 in case of retrieving mclk fails
>>>> to be backward compatible of new device tree with older kernels.
>>>>
>>>> Cc: stable@vger.kernel.org
>>>>
>>>> Signed-off-by: Sowjanya Komatineni <skomatineni@nvidia.com>
>>>> ---
>>>>    sound/soc/tegra/tegra_asoc_utils.c | 10 ++++++++--
>>>>    1 file changed, 8 insertions(+), 2 deletions(-)
>>> <formletter>
>>>
>>> This is not the correct way to submit patches for inclusion in the
>>> stable kernel tree.  Please read:
>>>       https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
>>> for how to do this properly.
>>>
>>> </formletter>
>> Hi Greg,
>>
>> link says to option-1 is strongly preferred for for all patches except for
>> submissions that are not in net/ and security related.
>>
>> Option-1 is to add Cc: stable@vger.kernel.org in sign-off area and I
>> followed this.
> That's fine, but then why did you just email a patch to yourself and the
> list?  Shouldn't you also submit the patch upstream to get it properly
> merged first?
>
> thanks,
>
> greg k-h

I set patches to the mailing list as per get_maintainers script.

Do I need to add any other alias to get patch applied for stable kernel 
other than cc tag?




-----------------------------------------------------------------------------------
This email message is for the sole use of the intended recipient(s) and may contain
confidential information.  Any unauthorized review, use, disclosure or distribution
is prohibited.  If you are not the intended recipient, please contact the sender by
reply email and destroy all copies of the original message.
-----------------------------------------------------------------------------------

  reply	other threads:[~2019-12-06 17:11 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1575600438-26795-1-git-send-email-skomatineni@nvidia.com>
2019-12-06  2:47 ` [PATCH v3 09/15] ASoC: tegra: Add fallback for audio mclk Sowjanya Komatineni
2019-12-06  7:09   ` Greg KH
2019-12-06 16:19     ` Sowjanya Komatineni
2019-12-06 16:29       ` Greg KH
2019-12-06 17:11         ` Sowjanya Komatineni [this message]
2019-12-06 17:15           ` Sowjanya Komatineni
2019-12-06 17:55             ` Greg KH
2019-12-06  2:48 [PATCH v3 00/15] Move PMC clocks into Tegra PMC driver Sowjanya Komatineni
2019-12-06  2:48 ` [PATCH v3 09/15] ASoC: tegra: Add fallback for audio mclk Sowjanya Komatineni
2019-12-06  2:48   ` Sowjanya Komatineni
2019-12-06 17:49   ` Sowjanya Komatineni
2019-12-06 17:49     ` Sowjanya Komatineni
2019-12-06 17:56     ` Greg KH
2019-12-09 16:40   ` Mark Brown
2019-12-09 20:31     ` Dmitry Osipenko
2019-12-09 20:47       ` Mark Brown
2019-12-10 18:24         ` Dmitry Osipenko
2019-12-10 18:59           ` Mark Brown
2019-12-12  2:17             ` Dmitry Osipenko

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=febf1f1a-6cca-c4d1-e220-50af5ef13ff7@nvidia.com \
    --to=skomatineni@nvidia.com \
    --cc=greg@kroah.com \
    --cc=stable@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.