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>,
Bard Liao <yung-chuan.liao@linux•intel.com>,
Pierre-Louis Bossart <pierre-louis.bossart@linux•intel.com>,
Daniel Baluta <daniel.baluta@nxp•com>
Subject: linux-next: Fixes tags needs some work in the sound-asoc tree
Date: Thu, 16 Apr 2020 09:41:11 +1000 [thread overview]
Message-ID: <20200416094111.3f37623f@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1086 bytes --]
Hi all,
In commit
101001652ee7 ("ASoC: SOF: topology: fix: handle DAI widget connections properly with multiple CPU DAI's")
Fixes tag
Fixes: 4a7e26a4d833 ("ASoC: SOF: topology: connect dai widget to all
has these problem(s):
- Target SHA1 does not exist
Maybe you meant
Fixes: c59aca98c912 ("ASoC: SOF: topology: connect dai widget to all cpu-dais")
Also, please do not split Fixes tags over more than one line and keep
all the commit message tags together at the end of the commit message.
In commit
cb0312f61c3e ("ASoC: SOF: imx: fix undefined reference issue")
Fixes tag
Fixes: f9ad75468453 ("ASoC: SOF: imx: fix reverse CONFIG_SND_SOC_SOF_OF
has these problem(s):
- Subject has leading but no trailing parentheses
- Subject has leading but no trailing quotes
Please do not split Fixes tags over more than one line.
Mark, since you don't seem to rebase your branches, please start pushing
back on these before they are committed to your tree (especially the
non existent SHA1s).
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2020-04-15 23:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-15 23:41 Stephen Rothwell [this message]
2020-04-16 12:55 ` linux-next: Fixes tags needs some work in the sound-asoc tree Pierre-Louis Bossart
2020-04-16 13:09 ` Mark Brown
2020-04-22 7:27 ` Daniel Baluta
2020-04-22 7:48 ` Mark Brown
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=20200416094111.3f37623f@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=broonie@kernel$(echo .)org \
--cc=daniel.baluta@nxp$(echo .)com \
--cc=lgirdwood@gmail$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=pierre-louis.bossart@linux$(echo .)intel.com \
--cc=yung-chuan.liao@linux$(echo .)intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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