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>,
Hariprasad Kelam <hkelam@marvell.com>,
Geetha sowjanya <gakula@marvell.com>,
Sunil Goutham <sgoutham@marvell.com>
Subject: linux-next: Fixes tags need some work in the net tree
Date: Thu, 1 Oct 2020 08:48:52 +1000 [thread overview]
Message-ID: <20201001084852.5bc93fca@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1205 bytes --]
Hi all,
In commit
66a5209b5341 ("octeontx2-pf: Fix synchnorization issue in mbox")
Fixes tag
Fixes: d424b6c02 ("octeontx2-pf: Enable SRIOV and added VF mbox handling")
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").
In commit
1ea0166da050 ("octeontx2-pf: Fix the device state on error")
Fixes tag
Fixes: 50fe6c02e ("octeontx2-pf: Register and handle link notifications")
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").
In commit
89eae5e87b4f ("octeontx2-pf: Fix TCP/UDP checksum offload for IPv6 frames")
Fixes tag
Fixes: 3ca6c4c88 ("octeontx2-pf: Add packet transmission support")
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:[~2020-09-30 22:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-30 22:48 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-01-12 19:50 Stephen Rothwell
2019-05-08 21:43 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=20201001084852.5bc93fca@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=davem@davemloft.net \
--cc=gakula@marvell.com \
--cc=hkelam@marvell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sgoutham@marvell.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).