From: Peter Ujfalusi <peter.ujfalusi@ti.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Mark Brown <broonie@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Fixes tag needs some work in the sound-asoc tree
Date: Fri, 26 Jul 2019 09:04:37 +0300 [thread overview]
Message-ID: <14710d5e-7dfd-84e0-2ea1-712863c4e455@ti.com> (raw)
In-Reply-To: <20190726072752.2acb2149@canb.auug.org.au>
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
next prev parent reply other threads:[~2019-07-26 6:04 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-25 21:27 linux-next: Fixes tag needs some work in the sound-asoc tree Stephen Rothwell
2019-07-26 6:04 ` Peter Ujfalusi [this message]
2019-07-26 12:11 ` Mark Brown
2019-07-29 5:57 ` Peter Ujfalusi
-- strict thread matches above, loose matches on Subject: below --
2023-11-13 20:58 Stephen Rothwell
2023-09-28 21:41 Stephen Rothwell
2022-07-19 22:22 Stephen Rothwell
2022-05-17 22:01 Stephen Rothwell
2022-04-28 0:57 Stephen Rothwell
2022-04-28 3:04 ` Tinghan Shen
2022-03-08 21:32 Stephen Rothwell
2022-03-02 21:01 Stephen Rothwell
2021-12-01 21:25 Stephen Rothwell
2021-12-02 9:29 ` Charles Keepax
2021-06-14 22:11 Stephen Rothwell
2021-05-12 22:40 Stephen Rothwell
2021-04-14 22:01 Stephen Rothwell
2020-07-29 22:04 Stephen Rothwell
2020-04-06 21:49 Stephen Rothwell
2020-03-29 0:09 Stephen Rothwell
2020-03-14 10:50 Stephen Rothwell
2020-03-16 8:21 ` Kai Vehmanen
2020-03-01 5:45 Stephen Rothwell
2020-02-24 22:30 Stephen Rothwell
2019-10-15 11:30 Stephen Rothwell
2019-10-15 11:35 ` Peter Ujfalusi
2019-08-20 22:25 Stephen Rothwell
2019-08-20 21:04 Stephen Rothwell
2019-08-20 22:27 ` Stephen Rothwell
2019-08-15 21:59 Stephen Rothwell
2019-08-15 21:34 Stephen Rothwell
2019-07-10 16:13 Stephen Rothwell
2019-07-11 0:40 ` Tzung-Bi Shih
2019-06-30 21:49 Stephen Rothwell
2019-06-26 13:42 Stephen Rothwell
2019-05-30 22:02 Stephen Rothwell
2019-05-21 21:31 Stephen Rothwell
2019-05-17 11:12 Stephen Rothwell
2019-05-17 2:41 S.j. Wang
2019-05-16 22:34 Stephen Rothwell
2019-03-18 11:18 Stephen Rothwell
2019-03-17 1:34 Stephen Rothwell
[not found] <CGME20190317012907epcas3p129240b3dcef7d974c2fea23c26a76f2a@epcas3p1.samsung.com>
2019-03-17 1:28 ` Stephen Rothwell
2019-03-18 10:08 ` Sylwester Nawrocki
2019-01-28 20:27 Stephen Rothwell
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=14710d5e-7dfd-84e0-2ea1-712863c4e455@ti.com \
--to=peter.ujfalusi@ti.com \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).