From: Dan Murphy <dmurphy@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-fixes tree
Date: Wed, 13 May 2020 16:20:32 -0500 [thread overview]
Message-ID: <f828c953-07b2-6a6b-881a-bf10f20a719d@ti.com> (raw)
In-Reply-To: <20200514071257.5b1582ca@canb.auug.org.au>
Stephen
On 5/13/20 4:12 PM, Stephen Rothwell wrote:
> Hi all,
>
> In commit
>
> 0e36f32f6b6c ("ASoC: tlv320adcx140: Fix bias config values")
>
> Fixes tag
>
> Fixes: 37bde5acf040 ("ASoC: tlv320adcx140: Add the tlv320adcx140 codec
>
> has these problem(s):
>
> - Target SHA1 does not exist
>
> Mabe you meant
>
> Fixes: 689c7655b50c ("ASoC: tlv320adcx140: Add the tlv320adcx140 codec driver family")
Yes this is what it is supposed to be
Mark
Did you want me to re-submit the patch with the corrected commit or are
you going to update it?
I also noticed code was spelled wrong in the commit message
s/conde/code
Dan
> Also, it looks like the Fixes tag had been split over more than one line
> (and then the latter part moved above the rest).
>
next prev parent reply other threads:[~2020-05-13 21:30 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-13 21:12 Stephen Rothwell
2020-05-13 21:20 ` Dan Murphy [this message]
2020-05-14 10:04 ` Mark Brown
-- strict thread matches above, loose matches on Subject: below --
2023-10-31 21:06 Stephen Rothwell
2021-12-16 13:00 Stephen Rothwell
2021-11-14 7:23 Stephen Rothwell
2021-06-01 22:00 Stephen Rothwell
2020-04-28 21:59 Stephen Rothwell
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=f828c953-07b2-6a6b-881a-bf10f20a719d@ti.com \
--to=dmurphy@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
all inboxes | Powered by JetHome®