All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <trini@ti.com>
To: linux-kernel@vger.kernel.org
Cc: Rusty Russell <rusty@rustcorp.com.au>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	linux-kbuild@vger.kernel.org
Subject: [PATCH] modpost.c: Add .text.unlikely to TEXT_SECTIONS
Date: Wed, 24 Apr 2013 18:26:03 -0400	[thread overview]
Message-ID: <1366842363-7513-1-git-send-email-trini@ti.com> (raw)

Recent gcc's may place functions into the .text.unlikely section and we
need to check this section as well for section mismatches now otherwise
we may have false negatives for this test.

Cc: Rusty Russell <rusty@rustcorp.com.au>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org
Cc: linux-kbuild@vger.kernel.org
Signed-off-by: Tom Rini <trini@ti.com>
---
 scripts/mod/modpost.c |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/scripts/mod/modpost.c b/scripts/mod/modpost.c
index ff36c50..13ff12f 100644
--- a/scripts/mod/modpost.c
+++ b/scripts/mod/modpost.c
@@ -880,7 +880,7 @@ static void check_section(const char *modname, struct elf_info *elf,
 #define ALL_EXIT_SECTIONS EXIT_SECTIONS, ALL_XXXEXIT_SECTIONS
 
 #define DATA_SECTIONS ".data$", ".data.rel$"
-#define TEXT_SECTIONS ".text$"
+#define TEXT_SECTIONS ".text$", ".text.unlikely$"
 
 #define INIT_SECTIONS      ".init.*"
 #define CPU_INIT_SECTIONS  ".cpuinit.*"
-- 
1.7.9.5


             reply	other threads:[~2013-04-24 22:25 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-24 22:26 Tom Rini [this message]
2013-04-29  2:59 ` [PATCH] modpost.c: Add .text.unlikely to TEXT_SECTIONS Rusty Russell
2013-04-29 13:15   ` Tom Rini
2013-04-29 13:15     ` Tom Rini
2013-05-01  2:19     ` Rusty Russell
2013-05-01 11:18       ` Tom Rini
2013-05-01 11:18         ` Tom Rini
2013-05-01 18:14         ` Tom Rini
2013-05-01 18:14           ` Tom Rini
2013-05-06  5:24           ` Rusty Russell

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=1366842363-7513-1-git-send-email-trini@ti.com \
    --to=trini@ti.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rusty@rustcorp.com.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 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.