From: Stephen Rothwell <sfr@canb.auug.org.au>
To: 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>,
Dan Murphy <dmurphy@ti.com>
Subject: linux-next: Fixes tag needs some work in the sound-asoc-fixes tree
Date: Wed, 29 Apr 2020 07:59:30 +1000 [thread overview]
Message-ID: <20200429075930.53910a3e@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 395 bytes --]
Hi all,
In commit
be8499c48f11 ("ASoC: tlv320adcx140: Fix mic gain registers")
Fixes tag
Fixes: 37bde5acf040 ("ASoC: tlv320adcx140: Add the tlv320adcx140 codec driver family")
has these problem(s):
- Target SHA1 does not exist
Maybe you meant
Fixes: 689c7655b50c ("ASoC: tlv320adcx140: Add the tlv320adcx140 codec driver family")
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2020-04-28 21:59 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-28 21:59 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-10-31 21:06 linux-next: Fixes tag needs some work in the sound-asoc-fixes tree Stephen Rothwell
2021-12-16 13:00 Stephen Rothwell
2021-11-14 7:23 Stephen Rothwell
2021-06-01 22:00 Stephen Rothwell
2020-05-13 21:12 Stephen Rothwell
2020-05-13 21:20 ` Dan Murphy
2020-05-14 10:04 ` Mark Brown
2020-04-14 22:00 Stephen Rothwell
2020-03-12 20:39 Stephen Rothwell
2020-03-01 5:38 Stephen Rothwell
2020-02-19 3:14 Stephen Rothwell
2020-01-19 1:13 Stephen Rothwell
2019-10-01 22:29 Stephen Rothwell
2019-10-02 7:55 ` Kai Vehmanen
2019-06-10 18:41 Stephen Rothwell
2019-06-06 22:01 Stephen Rothwell
2019-05-13 15:00 Stephen Rothwell
2019-04-10 21:00 Stephen Rothwell
2019-02-26 20:42 Stephen Rothwell
2019-02-07 20:31 Stephen Rothwell
2019-02-06 20:05 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=20200429075930.53910a3e@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=broonie@kernel.org \
--cc=dmurphy@ti.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@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.