From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: Dave Chinner <david@fromorbit.com>
Cc: bpm@sgi.com, linux-next@vger.kernel.org, cmetcalf@tilera.com,
xfs@oss.sgi.com
Subject: Re: Building tilegx defconfig gets init/exit section errors in xfs.
Date: Mon, 26 Mar 2012 18:10:25 -0400 [thread overview]
Message-ID: <4F70E951.50009@windriver.com> (raw)
In-Reply-To: <20120326215919.GN5091@dastard>
On 12-03-26 05:59 PM, Dave Chinner wrote:
> On Sun, Mar 25, 2012 at 02:20:35PM -0400, Paul Gortmaker wrote:
>> Hi All,
>>
>> Recently the tilegx defconfig was added to the linux-next build
>> coverage, which exposed this.
>>
>> LD .tmp_vmlinux1
>> `xfs_qm_exit' referenced in section `.init.text' of fs/built-in.o:
>> defined in discarded section `.exit.text' of fs/built-in.o
>> make[1]: *** [.tmp_vmlinux1] Error 1
>>
>> http://kisskb.ellerman.id.au/kisskb/buildresult/5941293/
>>
>> It seemed odd to me, since I didn't think there was anything arch
>> specific in the init/exit sectioning, so I thought I'd mention it
>> here, just in case it hasn't been brought up before.
>
> Already been reported, a patch has been provided, too. So the fix
> is underway.
>
> Thanks for reporting the problem anyway, Paul.
Thanks Dave, Ben - seems gmane archive isn't easily searchable, but
the nabble one is. I'll add this link to the linux-next triage
report until the fix appears in a linux-next build:
http://old.nabble.com/-PATCH--fs%3A-xfs%3A-fix-section-mismatch-in-linux-next-td33519270.html
And next time I'll try harder to search a useful archive. :)
Paul.
>
> Cheers,
>
> Dave.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2012-03-26 22:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-25 18:20 Building tilegx defconfig gets init/exit section errors in xfs Paul Gortmaker
2012-03-26 21:53 ` Ben Myers
2012-03-26 21:59 ` Dave Chinner
2012-03-26 22:10 ` Paul Gortmaker [this message]
2012-03-26 22:12 ` Chris Metcalf
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=4F70E951.50009@windriver.com \
--to=paul.gortmaker@windriver.com \
--cc=bpm@sgi.com \
--cc=cmetcalf@tilera.com \
--cc=david@fromorbit.com \
--cc=linux-next@vger.kernel.org \
--cc=xfs@oss.sgi.com \
/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