From: Al Viro <viro@ZenIV.linux.org.uk>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: David Howells <dhowells@redhat.com>,
linux-fsdevel@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [patch] VFS: copy_tree() returns an error pointer now
Date: Sat, 14 Jul 2012 13:10:02 +0100 [thread overview]
Message-ID: <20120714121002.GL22927@ZenIV.linux.org.uk> (raw)
In-Reply-To: <20120704073945.GA30520@elgon.mountain>
On Wed, Jul 04, 2012 at 10:39:45AM +0300, Dan Carpenter wrote:
> We recently changed copy_tree() to return an error pointer in
> d196d8d327 ('VFS: Make clone_mnt()/copy_tree()/collect_mounts() return
> errors'). This call needs to be updated as well.
Folded.
prev parent reply other threads:[~2012-07-14 12:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-04 7:39 [patch] VFS: copy_tree() returns an error pointer now Dan Carpenter
2012-07-04 9:45 ` David Howells
2012-07-14 12:10 ` Al Viro [this message]
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=20120714121002.GL22927@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=dan.carpenter@oracle.com \
--cc=dhowells@redhat.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-fsdevel@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).