From: Stephen Rothwell <sfr@canb.auug.org.au>
To: David Miller <davem@davemloft.net>, Networking <netdev@vger.kernel.org>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Vladimir Oltean <olteanv@gmail.com>,
Hangbin Liu <liuhangbin@gmail.com>
Subject: linux-next: Fixes tags need some work in the net tree
Date: Thu, 9 May 2019 07:43:08 +1000 [thread overview]
Message-ID: <20190509074308.7c0ade7d@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 805 bytes --]
Hi all,
In commit
3b2c4f4d63a5 ("net: dsa: sja1105: Don't return a negative in u8 sja1105_stp_state_get")
Fixes tag
Fixes: 640f763f98c2: ("net: dsa: sja1105: Add support for Spanning Tree Protocol")
has these problem(s):
- the ':' after the SHA1 is unexpected
Just use
git log -1 --format='Fixes: %h ("%s")'
In commit
e9919a24d302 ("fib_rules: return 0 directly if an exactly same rule exists when NLM_F_EXCL not supplied")
Fixes tag
Fixes: 153380ec4b9 ("fib_rules: Added NLM_F_EXCL support to fib_nl_newrule")
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-05-08 21:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-08 21:43 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-06-16 22:03 linux-next: Fixes tags need some work in the net tree Stephen Rothwell
2021-06-17 1:35 ` Joakim Zhang
2020-09-30 22:48 Stephen Rothwell
2020-01-12 19:50 Stephen Rothwell
2019-02-17 13:52 Stephen Rothwell
2019-01-29 20:49 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=20190509074308.7c0ade7d@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=liuhangbin@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.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;
as well as URLs for NNTP newsgroup(s).