[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAP01T74GyRjXRZaDA-E5CXeaoKaf+FegQFxNP9k6kt8cvbt+EA@mail.gmail.com>
Date: Wed, 24 Aug 2022 19:04:26 +0200
From: Kumar Kartikeya Dwivedi <memxor@...il.com>
To: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: Daniel Borkmann <daniel@...earbox.net>,
Alexei Starovoitov <ast@...nel.org>,
Andrii Nakryiko <andrii@...nel.org>, bpf <bpf@...r.kernel.org>,
Networking <netdev@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: Fixes tag needs some work in the bpf-next tree
On Wed, 24 Aug 2022 at 07:00, Stephen Rothwell <sfr@...b.auug.org.au> wrote:
>
> 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")
>
Ugh, really sorry, I must have fat fingered and pressed 'x' in vim
while editing the commit message. I always generate these using a git
fixes alias.
> --
> Cheers,
> Stephen Rothwell
Powered by blists - more mailing lists