dm-devel.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Christophe Varoqui <christophe.varoqui@gmail.com>
To: Benjamin Marzinski <bmarzins@redhat.com>
Cc: device-mapper development <dm-devel@redhat.com>
Subject: Re: [PATCH] multipath: Make sure we store all the hwentry attributes.
Date: Wed, 23 May 2012 22:37:23 +0200	[thread overview]
Message-ID: <1337805443.2890.4.camel@lapoo.opensvc.com> (raw)
In-Reply-To: <20120523202905.GE9924@ether.msp.redhat.com>

On mer., 2012-05-23 at 15:29 -0500, Benjamin Marzinski wrote:
> Not all of the attributes from the hardware table entries were getting stored
> when the built-in devices configurations were being setup.
> 
Applied.

> Signed-off-by: Benjamin Marzinski <bmarzins@redhat.com>
> ---
>  libmultipath/config.c |    4 ++++
>  1 file changed, 4 insertions(+)
> 
> Index: multipath-tools-120518/libmultipath/config.c
> ===================================================================
> --- multipath-tools-120518.orig/libmultipath/config.c
> +++ multipath-tools-120518/libmultipath/config.c
> @@ -379,6 +379,10 @@ store_hwe (vector hwtable, struct hwentr
>  	hwe->no_path_retry = dhwe->no_path_retry;
>  	hwe->minio = dhwe->minio;
>  	hwe->minio_rq = dhwe->minio_rq;
> +	hwe->pg_timeout = dhwe->pg_timeout;
> +	hwe->flush_on_last_del = dhwe->flush_on_last_del;
> +	hwe->fast_io_fail = dhwe->fast_io_fail;
> +	hwe->dev_loss = dhwe->dev_loss;
>  
>  	if (dhwe->bl_product && !(hwe->bl_product = set_param_str(dhwe->bl_product)))
>  		goto out;

      reply	other threads:[~2012-05-23 20:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-23 20:29 [PATCH] multipath: Make sure we store all the hwentry attributes Benjamin Marzinski
2012-05-23 20:37 ` Christophe Varoqui [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=1337805443.2890.4.camel@lapoo.opensvc.com \
    --to=christophe.varoqui@gmail.com \
    --cc=bmarzins@redhat.com \
    --cc=christophe.varoqui@opensvc.com \
    --cc=dm-devel@redhat.com \
    /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).