[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <14710d5e-7dfd-84e0-2ea1-712863c4e455@ti.com>
Date: Fri, 26 Jul 2019 09:04:37 +0300
From: Peter Ujfalusi <peter.ujfalusi@...com>
To: Stephen Rothwell <sfr@...b.auug.org.au>,
Mark Brown <broonie@...nel.org>,
Liam Girdwood <lgirdwood@...il.com>
CC: Linux Next Mailing List <linux-next@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: linux-next: Fixes tag needs some work in the sound-asoc tree
Stephen,
On 26/07/2019 0.27, Stephen Rothwell wrote:
> Hi all,
>
> In commit
>
> 9fcf9139a2fd ("ASoC: ti: davinci-mcasp: Fix clk PDIR handling for i2s master mode")
>
> Fixes tag
>
> Fixes: 2302be4126f52 ("ASoC: davinci-mcasp: Update PDIR (pin direction) register handling")
>
> has these problem(s):
>
> - Target SHA1 does not exist
>
> Did you mean
>
> Fixes: ca3d9433349e ("ASoC: davinci-mcasp: Update PDIR (pin direction) register handling")
Indeed this is the correct SHA1, looks like the 2302be4126f52 is on TI's
4.19-LTS branch and it got into the commit message because I have
validated first on that before moving on to linux-next.
Mark: can you either drop the patch and I'll send a new one with fixed
SHA1 or can you fix the commit message in place?
Sorry.
- Péter
Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki.
Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki
Powered by blists - more mailing lists