From: Artem Bityutskiy <Artem.Bityutskiy@nokia.com>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: next-2008-12-04: ubifs section fixlet
Date: Thu, 04 Dec 2008 16:18:22 +0200 [thread overview]
Message-ID: <4937E6AE.9040302@nokia.com> (raw)
In-Reply-To: <20081204140418.GB13953@x200.localdomain>
Alexey Dobriyan wrote:
> Please, fold into 552ff3179d1e93a3e982357544c059f3e9a5516e
> aka "UBIFS: add debugfs support":
>
> WARNING: fs/ubifs/ubifs.o(.init.text+0xec): Section mismatch in reference from the function init_module() to the function .exit.text:ubifs_compressors_exit()
Pushed to ubifs-2.6.git, thanks.
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
next prev parent reply other threads:[~2008-12-04 14:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-04 9:07 linux-next: Tree for December 4 Stephen Rothwell
2008-12-04 14:00 ` next-2008-12-04: ca0106 compile fix Alexey Dobriyan
2008-12-04 14:28 ` Takashi Iwai
2008-12-04 14:04 ` next-2008-12-04: ubifs section fixlet Alexey Dobriyan
2008-12-04 14:18 ` Artem Bityutskiy [this message]
2008-12-05 0:50 ` linux-next: Tree for December 4 (netdev-related: several) Randy Dunlap
2008-12-05 7:06 ` next-2008-12-04: vm.bio_inline_vecs Alexey Dobriyan
2008-12-05 8:44 ` Jens Axboe
[not found] ` <20081204200745.eff0ac87.sfr-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org>
2008-12-06 12:04 ` linux-next: Tree for December 4 Mariusz Kozlowski
[not found] ` <200812061304.12216.m.kozlowski-NWF1p15JEu3VItvQsEIGlw@public.gmane.org>
2008-12-06 13:42 ` Alexander Beregalov
2008-12-07 0:43 ` Stephen Rothwell
2008-12-09 7:07 ` next-20081104 - kernel panic on ia64 box, at __mutex_lock_interruptible_slowpath Kamalesh Babulal
2008-12-09 18:50 ` Luck, Tony
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=4937E6AE.9040302@nokia.com \
--to=artem.bityutskiy@nokia.com \
--cc=adobriyan@gmail.com \
--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 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).