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>,
Hauke Mehrtens <hauke.mehrtens@intel.com>,
Florian Fainelli <f.fainelli@gmail.com>
Subject: linux-next: Fixes tags need some work in the net tree
Date: Mon, 18 Feb 2019 00:52:03 +1100 [thread overview]
Message-ID: <20190218005203.5ac3473e@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 757 bytes --]
Hi all,
In commit
a40061ea2e39 ("net: systemport: Fix reception of BPDUs")
Fixes tag
Fixes: 4e8aedfe78c7 ("net: systemport: Turn on offloads by default")
has these problem(s):
- Target SHA1 does not exist
Did you mean
Fixes: b5061778f822 ("net: systemport: Turn on offloads by default")?
In commit
3b89ea9c5902 ("net: Fix for_each_netdev_feature on Big endian")
Fixes tag
Fixes: fd867d51f ("net/core: generic support for disabling netdev features down stack")
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-02-17 13:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-17 13:52 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-05-08 21:43 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=20190218005203.5ac3473e@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=hauke.mehrtens@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=netdev@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 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).