From: Randy Dunlap <rdunlap@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Josh Poimboeuf <jpoimboe@redhat.com>,
Peter Zijlstra <peterz@infradead.org>, bpf <bpf@vger.kernel.org>
Subject: Re: linux-next: Tree for Apr 10 (warning: objtool: ___bpf_prog_run())
Date: Sat, 11 Apr 2020 20:46:15 -0700 [thread overview]
Message-ID: <e9e6b603-4bd3-bf42-443c-10fae629680a@infradead.org> (raw)
In-Reply-To: <20200410132706.170811b7@canb.auug.org.au>
On 4/9/20 8:27 PM, Stephen Rothwell wrote:
> Hi all,
>
> The merge window has opened, so please do not add any material for the
> next release into your linux-next included trees/branches until after
> the merge window closes.
>
> Changes since 20200409:
>
Hi Josh,
In an x86_64 kernel built with FRAME_POINTER=y and UNWINDER_ORC not set,
do we care about this warning?
kernel/bpf/core.o: warning: objtool: ___bpf_prog_run()+0x33: call without frame pointer save/setup
thanks.
--
~Randy
Reported-by: Randy Dunlap <rdunlap@infradead.org>
prev parent reply other threads:[~2020-04-12 3:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-10 3:27 linux-next: Tree for Apr 10 Stephen Rothwell
2020-04-10 16:35 ` linux-next: Tree for Apr 10 (lib/test_printf.ko) Randy Dunlap
2020-04-10 18:11 ` Linus Torvalds
2020-04-10 18:29 ` Randy Dunlap
2020-04-10 19:05 ` Linus Torvalds
2020-04-10 19:41 ` Randy Dunlap
2020-04-10 20:13 ` Linus Torvalds
2020-04-12 5:36 ` Naresh Kamboju
2020-04-12 6:22 ` Randy Dunlap
2020-04-14 19:26 ` Brendan Higgins
2020-04-15 18:55 ` Steven Rostedt
2020-04-15 19:16 ` Randy Dunlap
2020-04-15 19:28 ` Steven Rostedt
2020-04-12 3:46 ` Randy Dunlap [this message]
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=e9e6b603-4bd3-bf42-443c-10fae629680a@infradead.org \
--to=rdunlap@infradead.org \
--cc=bpf@vger.kernel.org \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=sfr@canb.auug.org.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;
as well as URLs for NNTP newsgroup(s).