From: Steve French <smfrench@gmail.com>
To: linux-fsdevel <linux-fsdevel@vger.kernel.org>
Cc: "linux-cifs-client@lists.samba.org" <linux-cifs-client@lists.samba.org>
Subject: Re: How to best return errors on follow_link
Date: Mon, 18 May 2009 12:42:59 -0500 [thread overview]
Message-ID: <524f69650905181042n79fd6dbdna57eb30d5fdeea0a@mail.gmail.com> (raw)
In-Reply-To: <524f69650905181030x6206e818yadc45eaae288e4ef@mail.gmail.com>
On Mon, May 18, 2009 at 12:30 PM, Steve French <smfrench@gmail.com> wrote:
> Jeff noticed a problem with the error handling in cifs_follow_link
> that brought up a question about how follow_link is supposed to be
> handling errors. His change has a sideeffect of now
> Is it ok to return errors on follow_link - seems strange to return
> them indicectly via set_link?
Sorry about the typo indecently was supposed to be "indirectly"
(return errors on set_link) :)
--
Thanks,
Steve
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2009-05-18 17:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-18 17:30 How to best return errors on follow_link Steve French
2009-05-18 17:42 ` Steve French [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=524f69650905181042n79fd6dbdna57eb30d5fdeea0a@mail.gmail.com \
--to=smfrench@gmail.com \
--cc=linux-cifs-client@lists.samba.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).