All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christophe Varoqui <christophe.varoqui@free.fr>
To: Edward Goggin <egoggin@emc.com>
Cc: dm-devel@redhat.com, dave.wysochanski@redhat.com
Subject: RE: patch to discovery.c to still getpathpriorityforpaths with path state of PATH_DOWN
Date: Wed, 15 Nov 2006 23:58:15 +0100	[thread overview]
Message-ID: <1163631495.10466.147.camel@localhost.localdomain> (raw)
In-Reply-To: <6CCEAEDF4D06984A83F427424F47D6E4013D1554@CORPUSMX40A.corp.emc.com>

Le mercredi 15 novembre 2006 à 17:48 -0500, Edward Goggin a écrit :
> OK.  I was trying not to have to introduce another
> prio state because that approach just seems prone
> to error.
> 
Actually, the patch remove one (0) :)

> I'll give it a try tomorrow.
> 
Thanks.

  reply	other threads:[~2006-11-15 22:58 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-10 23:01 patch to discovery.c to still get path priority for paths with path state of PATH_DOWN Edward Goggin
2006-11-13 20:04 ` Dave Wysochanski
2006-11-13 20:47   ` patch to discovery.c to still get path priority forpaths " Edward Goggin
2006-11-14 14:26     ` Dave Wysochanski
2006-11-14 20:09       ` patch to discovery.c to still get path priorityforpaths " Edward Goggin
2006-11-15  6:48         ` Dave Wysochanski
2006-11-15 19:48           ` patch to discovery.c to still get pathpriorityforpaths " Edward Goggin
2006-11-15 20:28             ` Dave Wysochanski
2006-11-15 22:33             ` Christophe Varoqui
2006-11-15 22:43               ` David Wysochanski
2006-11-15 22:57                 ` Christophe Varoqui
2006-11-15 22:48               ` patch to discovery.c to still getpathpriorityforpaths " Edward Goggin
2006-11-15 22:58                 ` Christophe Varoqui [this message]
2006-11-15 23:09                 ` Dave Wysochanski
2006-11-17 13:49                   ` patch to discovery.c to stillgetpathpriorityforpaths " Edward Goggin
2006-11-17 21:06                     ` Christophe Varoqui

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=1163631495.10466.147.camel@localhost.localdomain \
    --to=christophe.varoqui@free.fr \
    --cc=dave.wysochanski@redhat.com \
    --cc=dm-devel@redhat.com \
    --cc=egoggin@emc.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.