Linux-Next Archive on lore.kernel.org
 help / color / Atom feed
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>,
	Tonghao Zhang <xiangxia.m.yue@gmail.com>
Subject: linux-next: Fixes tag needs some work in the net-next tree
Date: Tue, 5 Nov 2019 08:01:34 +1100
Message-ID: <20191105080134.33aab6a1@canb.auug.org.au> (raw)


[-- Attachment #1: Type: text/plain, Size: 460 bytes --]

Hi all,

In commit

  4c76bf696a60 ("net: openvswitch: don't unlock mutex when changing the user_features fails")

Fixes tag

  Fixes: 95a7233c4 ("net: openvswitch: Set OvS recirc_id from tc chain index")

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 --]

             reply index

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-04 21:01 Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-04-18 21:53 Stephen Rothwell
2021-03-30  1:15 Stephen Rothwell
2021-03-26 23:03 Stephen Rothwell
2020-09-15 23:04 Stephen Rothwell
2020-06-01 23:12 Stephen Rothwell
2020-06-02  7:31 ` Ayush Sawal
2020-06-02 10:18   ` Stephen Rothwell
2020-06-02 10:30     ` Ayush Sawal
2020-04-22 22:16 Stephen Rothwell
2020-02-27  4:42 Stephen Rothwell
2020-02-27  9:01 ` Maxim Mikityanskiy
2020-02-17  4:23 Stephen Rothwell
2019-12-18  6:35 Stephen Rothwell
2019-09-10 14:37 Stephen Rothwell
2019-08-01 22:54 Stephen Rothwell
2019-07-29 21:25 Stephen Rothwell
2019-07-22 21:35 Stephen Rothwell
     [not found] ` <CANP3RGcqGrPnt9eOiAKRbxWVuBkRHRQdWPnANKwrYvtVnTqaSQ@mail.gmail.com>
2019-07-23  0:49   ` Stephen Rothwell
2019-07-03 21:42 Stephen Rothwell
2019-06-30 21:37 Stephen Rothwell
2019-04-22 21:26 Stephen Rothwell
2019-04-23 12:19 ` John Hurley
2019-04-05  5:58 Stephen Rothwell
2019-03-21 18:54 Stephen Rothwell
2019-02-25  8:00 Stephen Rothwell
2019-02-27  1:12 ` tanhuazhong
2019-02-27  2:23   ` Stephen Rothwell
2019-02-27  3:16     ` tanhuazhong
2019-02-19 22:31 Stephen Rothwell
2019-02-20  4:40 ` Vinod Koul
2019-02-20  5:38   ` Stephen Rothwell
2019-02-20  6:48   ` David Miller
2019-02-20  8:36     ` Jiri Pirko
2019-02-20 19:02       ` David Miller
2019-02-20 19:58         ` Jiri Pirko
2019-02-20 20:25           ` David Miller
2019-02-20 20:26             ` Jiri Pirko
2019-02-20 19:59         ` Stefano Brivio
2019-02-20 20:25           ` David Miller
2019-02-20 20:37             ` Stefano Brivio
2019-02-20 20:42               ` David Miller
2019-02-21  5:34           ` Vinod Koul
2019-02-11 22:17 Stephen Rothwell
2019-01-31 20:35 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=20191105080134.33aab6a1@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=netdev@vger.kernel.org \
    --cc=xiangxia.m.yue@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

Linux-Next Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-next/0 linux-next/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-next linux-next/ https://lore.kernel.org/linux-next \
		linux-next@vger.kernel.org
	public-inbox-index linux-next

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-next


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git