From: Artem Bityutskiy <Artem.Bityutskiy@nokia.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: "linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Corentin Chary <corentincj@iksaif.net>
Subject: Re: linux-next: ubifs tree build failure
Date: Tue, 24 Nov 2009 08:31:54 +0200 [thread overview]
Message-ID: <1259044314.18407.51.camel@localhost> (raw)
In-Reply-To: <20091124121415.dc1e98a0.sfr@canb.auug.org.au>
On Tue, 2009-11-24 at 02:14 +0100, Stephen Rothwell wrote:
> Hi Artem,
>
> Today's linux-next build (x86_64 allmodconfig) failed like this:
>
> fs/ubifs/super.c: In function 'open_ubi':
> fs/ubifs/super.c:1866: error: implicit declaration of function 'ubi_open_volume_path'
> fs/ubifs/super.c:1866: warning: assignment makes pointer from integer without a cast
>
> Caused by commit 82ccbf8c4ec2113d4e73dbac3ca914019ca883ca ("UBIFS:
> support mounting of UBI volume character devices") which I have reverted
> for today.
Stephen,
thanks for quick reaction and sorry for the hassle. I've just fixed this
up.
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
next prev parent reply other threads:[~2009-11-24 6:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-24 1:14 linux-next: ubifs tree build failure Stephen Rothwell
2009-11-24 6:31 ` Artem Bityutskiy [this message]
2009-11-24 7:28 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2008-08-12 6:24 Stephen Rothwell
2008-08-12 7:11 ` Artem Bityutskiy
2008-08-12 7:37 ` Artem Bityutskiy
2008-08-12 8:42 ` Stephen Rothwell
2008-08-12 18:24 ` Christoph Hellwig
2008-08-13 9:42 ` Artem Bityutskiy
2008-08-12 18:24 ` Christoph Hellwig
2008-08-12 21:39 ` Christoph Hellwig
2008-08-13 6:23 ` Artem Bityutskiy
2008-08-13 9:58 ` Artem Bityutskiy
2008-08-13 11:20 ` 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=1259044314.18407.51.camel@localhost \
--to=artem.bityutskiy@nokia.com \
--cc=corentincj@iksaif.net \
--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.