From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Carlos Maiolino <cmaiolino@redhat.com>
Cc: linux-xfs@vger.kernel.org
Subject: Re: [PATCH] Fix max_retries _show and _store functions
Date: Tue, 3 Jan 2017 21:58:03 -0800 [thread overview]
Message-ID: <20170104055803.GE14031@birch.djwong.org> (raw)
In-Reply-To: <20170103175331.8089-1-cmaiolino@redhat.com>
On Tue, Jan 03, 2017 at 06:53:31PM +0100, Carlos Maiolino wrote:
> max_retries _show and _store functions should test against cfg->max_retries,
> not cfg->retry_timeout
>
> Signed-off-by: Carlos Maiolino <cmaiolino@redhat.com>
> ---
> fs/xfs/xfs_sysfs.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/fs/xfs/xfs_sysfs.c b/fs/xfs/xfs_sysfs.c
> index 276d302..de6195e 100644
> --- a/fs/xfs/xfs_sysfs.c
> +++ b/fs/xfs/xfs_sysfs.c
> @@ -396,7 +396,7 @@ max_retries_show(
> int retries;
> struct xfs_error_cfg *cfg = to_error_cfg(kobject);
>
> - if (cfg->retry_timeout == XFS_ERR_RETRY_FOREVER)
> + if (cfg->max_retries == XFS_ERR_RETRY_FOREVER)
> retries = -1;
> else
> retries = cfg->max_retries;
> @@ -422,7 +422,7 @@ max_retries_store(
> return -EINVAL;
>
> if (val == -1)
> - cfg->retry_timeout = XFS_ERR_RETRY_FOREVER;
> + cfg->max_retries = XFS_ERR_RETRY_FOREVER;
Applied, thanks.
--D
> else
> cfg->max_retries = val;
> return count;
> --
> 2.9.3
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-xfs" 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:[~2017-01-04 5:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-03 17:53 [PATCH] Fix max_retries _show and _store functions Carlos Maiolino
2017-01-03 18:19 ` Eric Sandeen
2017-01-04 10:58 ` Carlos Maiolino
2017-01-04 15:46 ` Eric Sandeen
2017-01-04 5:58 ` Darrick J. Wong [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=20170104055803.GE14031@birch.djwong.org \
--to=darrick.wong@oracle.com \
--cc=cmaiolino@redhat.com \
--cc=linux-xfs@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.