All of lore.kernel.org
 help / color / mirror / Atom feed
From: Theodore Tso <tytso@mit.edu>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: ext4 tree build warning
Date: Fri, 28 Aug 2009 09:50:04 -0400	[thread overview]
Message-ID: <20090828135004.GG16732@mit.edu> (raw)
In-Reply-To: <20090827171704.28109c6f.sfr@canb.auug.org.au>

On Thu, Aug 27, 2009 at 05:17:04PM +1000, Stephen Rothwell wrote:
> Hi Ted,
> 
> The linux-next builds (ppc64 allyesconfig) produce this warning:
> (I built with CONFIG_DEBUG_SECTION_MISMATCH=y)
> 
> WARNING: fs/ext4/ext4.o(.text+0x5b6c8): Section mismatch in reference from the function .exit_ext4_mballoc() to the function .exit.text:.ext4_remove_debugfs_entry()
> The function .exit_ext4_mballoc() references a function in an exit section.
> Often the function .ext4_remove_debugfs_entry() has valid usage outside the exit section
> and the fix is to remove the __exit annotation of .ext4_remove_debugfs_entry.

Thanks for pointing that out, I'll get that fixed.

						- Ted

  reply	other threads:[~2009-08-28 13:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-27  7:17 linux-next: ext4 tree build warning Stephen Rothwell
2009-08-28 13:50 ` Theodore Tso [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-10-02  1:26 Stephen Rothwell
2009-10-03  1:03 ` Theodore Tso
2009-06-16  1:08 Stephen Rothwell
2009-06-09  0:54 Stephen Rothwell
2009-06-09  4:23 ` Theodore Tso
2009-06-09  7:11   ` Stephen Rothwell
2009-03-30  4:48 Stephen Rothwell

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=20090828135004.GG16732@mit.edu \
    --to=tytso@mit.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.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 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.