From: Dan Carpenter <dan.carpenter@oracle.com>
To: Christophe Leroy <christophe.leroy@csgroup.eu>
Cc: "kbuild@lists.01.org" <kbuild@lists.01.org>,
"lkp@intel.com" <lkp@intel.com>,
"kbuild-all@lists.01.org" <kbuild-all@lists.01.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Michael Ellerman <mpe@ellerman.id.au>
Subject: Re: [kbuild] arch/powerpc/net/bpf_jit_comp.c:225 bpf_int_jit_compile() error: uninitialized symbol 'pass'.
Date: Fri, 4 Feb 2022 17:14:59 +0300 [thread overview]
Message-ID: <20220204141459.GJ1978@kadam> (raw)
In-Reply-To: <45bd66d4-14b8-bdb0-7d6c-096d6d7cddb6@csgroup.eu>
On Fri, Feb 04, 2022 at 01:18:24PM +0000, Christophe Leroy wrote:
> Hi Dan,
>
> Le 04/02/2022 à 11:37, Dan Carpenter a écrit :
> > tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> > head: 88808fbbead481aedb46640a5ace69c58287f56a
> > commit: 51c66ad849a703d9bbfd7704c941827aed0fd9fd powerpc/bpf: Implement extended BPF on PPC32
>
> As far as I can see, it's been there long before that.
>
> Seems it comes from 025dceb0fab3 ("bpf: powerpc64: optimize JIT passes
> for bpf function calls")
These emails are auto generated by bot. I just look over the email and
verify it looks reasonable. Moving the code around sometimes makes it
show up as a new bug. Also changes to the Kconfig file can affect which
code is checked.
The commit that you mention does not generate a warning. The warning
started in commit 025dceb0fab3 ("bpf: powerpc64: optimize JIT passes for
bpf function calls").
regards,
dan carpenter
next prev parent reply other threads:[~2022-02-04 14:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-04 10:37 Dan Carpenter
2022-02-04 13:18 ` Christophe Leroy
2022-02-04 14:14 ` Dan Carpenter [this message]
2022-02-04 14:24 ` Christophe Leroy
2022-02-04 14:30 ` Dan Carpenter
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=20220204141459.GJ1978@kadam \
--to=dan.carpenter@oracle.com \
--cc=christophe.leroy@csgroup.eu \
--cc=kbuild-all@lists.01.org \
--cc=kbuild@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=mpe@ellerman.id.au \
/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
all inboxes | Powered by JetHome®