From: Chris Gentile <cnjgentile@gmail.com>
To: Mathieu Belanger <m@thieu.so>
Cc: Evgeniy <iron.udjin@gmail.com>,
Edward Shishkin <edward.shishkin@gmail.com>,
reiserfs-devel@vger.kernel.org
Subject: Re: Reiser4 GIT and Kernel 3.11 patchs
Date: Wed, 18 Sep 2013 06:47:05 +0000 [thread overview]
Message-ID: <52394C69.8060702@gmail.com> (raw)
In-Reply-To: <20130918062035.Horde.3REQSHqc8XUbgvTNKMOnnw1@mail.thieu.so>
On 3.12-rc1 branch I get the following errors:
fs/fs-writeback.c: In function 'generic_writeback_sb_inodes':
fs/fs-writeback.c:641:3: warning: passing argument 2 of
'__writeback_single_inode' from incompatible pointer type [enabled by
default]
__writeback_single_inode(inode, &wbc);
^
fs/fs-writeback.c:414:1: note: expected 'struct writeback_control *' but
argument is of type 'struct writeback_control **'
__writeback_single_inode(struct inode *inode, struct writeback_control
*wbc)
and
include/linux/dcache.h:104:25: error: expected '=', ',', ';', 'asm' or
'__attribute__' before '.' token
#define d_lock d_lockref.lock
^
fs/reiser4/fsdata.h:192:19: note: in expansion of macro 'd_lock'
extern spinlock_t d_lock
during compile. Stops dead in it's tracks when linking fs/nfs/built-in.so
Is it a simple fix ? Maybe I can edit a in the kernel tree?
On 09/18/13 06:20, Mathieu Belanger wrote:
> Yes, I have messed-up my git commands.
>
> Now you can pull the new branch (listed there
> https://github.com/DestroyFX/reiser4/branches )
>
> For "real" kernel 3.11-rc4, 3.11 and 3.12-rc1.
>
> I did not test the compilation on 3.11+, I just took the patch for
> 3.11-rc4 and applied on others one.
>
next prev parent reply other threads:[~2013-09-18 6:47 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-17 18:15 Reiser4 GIT and Kernel 3.11 patchs Mathieu Belanger
2013-09-17 19:52 ` Edward Shishkin
2013-09-17 20:24 ` Evgeniy
2013-09-17 20:37 ` Chris Gentile
2013-09-17 21:02 ` Evgeniy
2013-09-17 21:15 ` Mathieu Belanger
2013-09-17 21:22 ` Chris Gentile
2013-09-17 22:02 ` Chris Gentile
2013-09-18 3:44 ` Mathieu Belanger
2013-09-18 5:52 ` Chris Gentile
2013-09-18 6:14 ` Chris Gentile
2013-09-18 6:20 ` Mathieu Belanger
2013-09-18 6:47 ` Chris Gentile [this message]
2013-09-18 6:54 ` Mathieu Belanger
2013-09-18 6:59 ` Chris Gentile
2013-09-18 13:20 ` Evgeniy
2013-09-18 13:27 ` Chris Gentile
2013-09-18 13:30 ` Chris Gentile
2013-09-18 14:02 ` Evgeniy
2013-09-18 15:53 ` Evgeniy
2013-09-18 16:09 ` Mathieu Belanger
2013-09-18 16:20 ` Mathieu Belanger
2013-09-18 16:24 ` Evgeniy
2013-09-18 16:39 ` Mathieu Belanger
2013-09-18 18:02 ` Evgeniy
2013-09-18 18:20 ` Mathieu Belanger
2013-09-18 18:36 ` Mathieu Belanger
2013-09-18 23:24 ` Mathieu Belanger
2013-09-18 23:36 ` Edward Shishkin
2013-09-19 1:25 ` Mathieu Belanger
[not found] ` <CADW=+3=znbq=KDqCmzQ_eq=V_9i4VpHj_uOcB3joJbZUZPNtdA@mail.gmail.com>
2013-09-19 5:45 ` Mathieu Belanger
2013-09-19 9:12 ` Edward Shishkin
2013-09-19 10:10 ` Evgeniy
2013-09-19 10:23 ` Evgeniy
2013-09-19 10:24 ` Edward Shishkin
2013-09-19 15:02 ` Christopher Gentile
2013-09-19 14:43 ` Christopher Gentile
[not found] ` <5238C666.6080703@gmail.com>
2013-09-17 21:22 ` Evgeniy
2013-09-17 21:25 ` Chris Gentile
2013-09-17 21:35 ` Evgeniy
[not found] ` <CAL2jS+mhmvmse7UqK4Xa0pYLSBJ9mfBDohKYFKdjzpAbL-=prA@mail.gmail.com>
2013-09-17 23:13 ` Edward Shishkin
-- strict thread matches above, loose matches on Subject: below --
2013-09-19 15:14 m
2013-09-19 15:55 ` Mathieu Belanger
2013-09-19 16:08 ` Christopher Gentile
2013-09-19 16:21 ` Christopher Gentile
2013-09-19 18:09 ` Mathieu Belanger
2013-09-19 20:05 ` Edward Shishkin
2013-09-19 18:16 ` Christopher Gentile
2013-09-23 19:01 ` Edward Shishkin
2013-09-23 21:21 ` Edward Shishkin
2013-09-24 9:08 ` Chris Gentile
2013-09-25 0:31 ` Mathieu Belanger
2013-09-25 0:34 ` Chris Gentile
2013-09-28 16:06 ` Chris Gentile
2013-09-25 4:47 ` Chris Gentile
2013-09-28 16:20 m
2013-09-28 17:43 ` Chris Gentile
[not found] ` <20130928174954.Horde.5eBFCXLtsWAtF9zNtt95nQ1@mail.thieu.so>
2013-09-28 18:22 ` Chris Gentile
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=52394C69.8060702@gmail.com \
--to=cnjgentile@gmail.com \
--cc=edward.shishkin@gmail.com \
--cc=iron.udjin@gmail.com \
--cc=m@thieu.so \
--cc=reiserfs-devel@vger.kernel.org \
/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).