From: Kiyoshi Ueda <k-ueda@ct.jp.nec.com>
To: Ritesh Raj Sarraf <rrs@researchut.com>
Cc: device-mapper development <dm-devel@redhat.com>
Subject: Re: [PATCH] Read the verbosity level from multipath.conf configuration file
Date: Fri, 21 Nov 2008 16:58:30 +0900 [thread overview]
Message-ID: <49266A26.7040801@ct.jp.nec.com> (raw)
In-Reply-To: <1227184875-20831-1-git-send-email-rsarraf@netapp.com>
Hi Ritesh,
rrs@researchut.com wrote:
> From: Ritesh Raj Sarraf <rrs@researchut.com>
>
> With this patch, multipathd can read the verbosity level from
> the multipath.conf configuration file.
> For example:
> verbosity 5
snip
> @@ -1316,6 +1327,14 @@ snprint_def_polling_interval (char * buff, int len, void * data)
> }
>
> static int
> +snprint_def_verbosity (char * buff, int len, void * data)
> +{
> + if (conf->checkint == DEFAULT_VERBOSITY)
Isn't it conf->verbosity?
Thanks,
Kiyoshi Ueda
next prev parent reply other threads:[~2008-11-21 7:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-20 12:41 [PATCH] Read the verbosity level from multipath.conf configuration file rrs
2008-11-21 7:58 ` Kiyoshi Ueda [this message]
2008-11-21 10:55 ` Ritesh Raj Sarraf
-- strict thread matches above, loose matches on Subject: below --
2008-11-21 10:54 Ritesh Raj Sarraf
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=49266A26.7040801@ct.jp.nec.com \
--to=k-ueda@ct.jp.nec.com \
--cc=dm-devel@redhat.com \
--cc=rrs@researchut.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 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.