All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Daniel Borkmann <daniel@iogearbox.net>,
	Alexei Starovoitov <ast@kernel.org>,
	Andrii Nakryiko <andrii@kernel.org>, bpf <bpf@vger.kernel.org>,
	Networking <netdev@vger.kernel.org>
Cc: Kumar Kartikeya Dwivedi <memxor@gmail.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: Fixes tag needs some work in the bpf-next tree
Date: Wed, 24 Aug 2022 15:00:51 +1000	[thread overview]
Message-ID: <20220824150051.54eb7748@canb.auug.org.au> (raw)

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

Hi all,

In commit

  2e5e0e8ede02 ("bpf: Fix reference state management for synchronous callbacks")

Fixes tag

  Fixes: 69c87ba6225 ("bpf: Add bpf_for_each_map_elem() helper")

has these problem(s):

  - Target SHA1 does not exist

Maybe you meant

Fixes: 69c087ba6225 ("bpf: Add bpf_for_each_map_elem() helper")

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

             reply	other threads:[~2022-08-24  5:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-24  5:00 Stephen Rothwell [this message]
2022-08-24 17:04 ` linux-next: Fixes tag needs some work in the bpf-next tree Kumar Kartikeya Dwivedi
2022-08-25  0:56   ` Alexei Starovoitov
  -- strict thread matches above, loose matches on Subject: below --
2022-03-17 21:14 Stephen Rothwell
2021-10-07 21:31 Stephen Rothwell
2021-10-07 21:56 ` Daniel Borkmann
2020-08-01 11:00 Stephen Rothwell
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=20220824150051.54eb7748@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=memxor@gmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.