From: Alexey Dobriyan <adobriyan@gmail.com>
To: jpoimboe@redhat.com, peterz@infradead.org
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH] objtool: bump function name limit to 256 characters
Date: Fri, 20 Sep 2019 21:25:03 +0300 [thread overview]
Message-ID: <20190920182503.GA15073@avx2> (raw)
Fix the following warning:
net/core/devlink.o: warning: objtool: _ZL31devlink_nl_sb_tc_pool_bind_fillP7sk_buffP7devlinkP12devlink_portP10devlink_sbt20devlink_sb_pool_type15devlink_commandjji.constprop.0.cold(): parent function name exceeds maximum length of 128 characters
Signed-off-by: Alexey Dobriyan <adobriyan@gmail.com>
---
tools/objtool/elf.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- a/tools/objtool/elf.c
+++ b/tools/objtool/elf.c
@@ -19,7 +19,7 @@
#include "elf.h"
#include "warn.h"
-#define MAX_NAME_LEN 128
+#define MAX_NAME_LEN 256
struct section *find_section_by_name(struct elf *elf, const char *name)
{
next reply other threads:[~2019-09-20 18:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-20 18:25 Alexey Dobriyan [this message]
2019-09-20 19:40 ` [PATCH] objtool: bump function name limit to 256 characters Josh Poimboeuf
2019-09-21 8:34 ` Alexey Dobriyan
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=20190920182503.GA15073@avx2 \
--to=adobriyan@gmail.com \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.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).