From: Edward Shishkin <edward.shishkin@gmail.com>
To: intelfx@intelfx.name,
Reiserfs development mailing list
<reiserfs-devel@vger.kernel.org>
Subject: Re: [PATCH] reiser4: port for Linux-4.5
Date: Wed, 6 Apr 2016 17:23:50 +0200 [thread overview]
Message-ID: <57052A06.2020207@gmail.com> (raw)
In-Reply-To: <1459905738.31752.7.camel@intelfx.name>
On 04/06/2016 03:22 AM, Ivan Shapovalov wrote:
> On 2016-03-30 at 11:20 +0200, Edward Shishkin wrote:
>> . Adjust for the new ->get_link() of vfs's inode_operations: we don't
>> support RCU mode;
>> . check returned value of __copy_from_user() to make gcc happy
>> (the path is never invoked) in create_item_node40().
>>
>> Signed-off-by: Edward Shishkin <edward.shishkin@gmail.com>
> By the way: I've noticed many times that the resulting squashed patch
> which you put on sourceforge is _different_ from what can be composed
> using incremental patches you send on the ML.
I never announced any peculiar properties of the patches that I
send to the mailing list. This is mostly for me (to look at the mail
archive and to refresh memory.
>
> Maybe you could finally consider having a git repo somewhere (e. g. on
> github)? It would be much easier to work with the code (and, for me in
> particular, to learn how it works) this way.
I'll consider it sooner or later, since all Namesys archives are
git-based, but it seems that probably "later", because currently I am
very busy..
Edward.
next prev parent reply other threads:[~2016-04-06 15:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-30 9:20 [PATCH] reiser4: port for Linux-4.5 Edward Shishkin
2016-04-06 0:42 ` Ivan Shapovalov
2016-04-06 15:21 ` Edward Shishkin
2016-04-06 15:26 ` Ivan Shapovalov
2016-04-06 1:22 ` Ivan Shapovalov
2016-04-06 15:23 ` Edward Shishkin [this message]
2016-04-06 15:37 ` Ivan Shapovalov
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=57052A06.2020207@gmail.com \
--to=edward.shishkin@gmail.com \
--cc=intelfx@intelfx.name \
--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 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.