All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrey Borzenkov <arvidjaar@mail.ru>
To: linux-hotplug@vger.kernel.org
Subject: Re: [PATCH] Add fc_id, which gives ID_PORT_NAME and ID_LUN on appropriate devices.
Date: Wed, 22 Jul 2009 02:47:03 +0000	[thread overview]
Message-ID: <200907220647.03748.arvidjaar@mail.ru> (raw)
In-Reply-To: <1248203904-6561-1-git-send-email-pjones@redhat.com>

[-- Attachment #1: Type: Text/Plain, Size: 510 bytes --]

On Tuesday 21 of July 2009 23:23:46 Peter Jones wrote:
> This makes it easier for consumers to use the individual pieces of
> information instead of having to parse path_id's output.
>
> + * report Fibre Channel Path Name and Lun

Path?

> +
> +	printf("ID_PORT_NAME=%s\n", port);

Could it be made ID_WWPN? In this case anyone working with SAN 
immediately knows what it means. PORT_NAME is less widespread.

ID_WWNN could potentially be useful as well if we already has utility to 
parse it.

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

      parent reply	other threads:[~2009-07-22  2:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-21 19:18 [PATCH] Add fc_id, which gives ID_PORT_NAME and ID_LUN on appropriate devices Peter Jones
2009-07-21 19:23 ` Peter Jones
2009-07-21 20:29 ` [PATCH] Add fc_id, which gives ID_PORT_NAME and ID_LUN on David Zeuthen
2009-07-21 21:07 ` [PATCH] Add fc_id, which gives ID_PORT_NAME and ID_LUN on appropriate Peter Jones
2009-07-21 22:04 ` [PATCH] Add fc_id, which gives ID_PORT_NAME and ID_LUN on Kay Sievers
2009-07-22  2:47 ` Andrey Borzenkov [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=200907220647.03748.arvidjaar@mail.ru \
    --to=arvidjaar@mail.ru \
    --cc=linux-hotplug@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.