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>,
Ranjani Sridharan <ranjani.sridharan@linux.intel.com>,
Arnaud Pouliquen <arnaud.pouliquen@st.com>
Subject: linux-next: Fixes tags need some work in the sound-asoc tree
Date: Tue, 9 Apr 2019 07:27:20 +1000 [thread overview]
Message-ID: <20190409072720.0f51ff2b@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1020 bytes --]
Hi all,
In commit
b4ed6b51f356 ("ASoC: core: conditionally increase module refcount on component open")
Fixes tag
Fixes: b450b878('ASoC: core: don't increase component module refcount
has these problem(s):
- missing space between the SHA1 and the subject
- SHA1 should be at least 12 digits long
Can be fixed by setting core.abbrev to 12 (or more) or (for git v2.11
or later) just making sure it is not set (or set to "auto").
- Subject has leading but no trailing parentheses
- Subject has leading but no trailing quotes
Please do not wrap FIxes tags over more than one line.
In commit
17d3069ccf06 ("ASoC: stm32: fix sai driver name initialisation")
Fixes tag
Fixes: 3e086ed ("ASoC: stm32: add SAI driver")
has these problem(s):
- SHA1 should be at least 12 digits long
Can be fixed by setting core.abbrev to 12 (or more) or (for git v2.11
or later) just making sure it is not set (or set to "auto").
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2019-04-08 21:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-08 21:27 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-05-28 21:56 linux-next: Fixes tags need some work in the sound-asoc tree Stephen Rothwell
2019-05-28 21:57 ` Stephen Rothwell
2019-05-28 22:22 ` Pierre-Louis Bossart
2019-05-29 0:00 ` 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=20190409072720.0f51ff2b@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=arnaud.pouliquen@st.com \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=ranjani.sridharan@linux.intel.com \
/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