From: Ivan Shapovalov <intelfx@intelfx.name>
To: Edward Shishkin <edward.shishkin@gmail.com>,
Reiserfs development mailing list
<reiserfs-devel@vger.kernel.org>
Subject: Re: [PATCH] reiser4: port for Linux-4.5
Date: Wed, 06 Apr 2016 18:26:23 +0300 [thread overview]
Message-ID: <1459956383.5177.0.camel@intelfx.name> (raw)
In-Reply-To: <57052985.8000905@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 796 bytes --]
On 2016-04-06 at 17:21 +0200, Edward Shishkin wrote:
> Which "adjustments" do you mean?
>
>
> On 04/06/2016 02:42 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>
> > Hi Edward,
> >
> > could you please send a separate patch with adjustments for 4.4?
> >
> > Thanks,
I meant usual forward-porting changes. But now I see that there were
none :) Sorry for the noise.
--
Ivan Shapovalov / intelfx /
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-04-06 15:26 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 [this message]
2016-04-06 1:22 ` Ivan Shapovalov
2016-04-06 15:23 ` Edward Shishkin
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=1459956383.5177.0.camel@intelfx.name \
--to=intelfx@intelfx.name \
--cc=edward.shishkin@gmail.com \
--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).