linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Daniel Borkmann <daniel@iogearbox.net>,
	Alexei Starovoitov <ast@kernel.org>,
	Networking <netdev@vger.kernel.org>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Jerry Crunchtime <jerry.c.t@web.de>
Subject: linux-next: Fixes tag needs some work in the bpf-next tree
Date: Sat, 1 Aug 2020 21:00:30 +1000	[thread overview]
Message-ID: <20200801210030.05d28152@canb.auug.org.au> (raw)

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

Hi all,

In commit

  1acf8f90ea7e ("libbpf: Fix register in PT_REGS MIPS macros")

Fixes tag

  Fixes: c1932cd ("bpf: Add MIPS support to samples/bpf.")

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	other threads:[~2020-08-01 11:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-01 11:00 Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-08-24  5:00 linux-next: Fixes tag needs some work in the bpf-next tree Stephen Rothwell
2022-08-24 17:04 ` Kumar Kartikeya Dwivedi
2022-08-25  0:56   ` Alexei Starovoitov
2022-03-17 21:14 Stephen Rothwell
2021-10-07 21:31 Stephen Rothwell
2021-10-07 21:56 ` Daniel Borkmann
2019-08-16 13:46 Stephen Rothwell
2019-08-16 14:35 ` Quentin Monnet

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=20200801210030.05d28152@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=ast@kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=jerry.c.t@web.de \
    --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).