From mboxrd@z Thu Jan  1 00:00:00 1970
From: Andrey Borzenkov <arvidjaar@mail.ru>
Date: Wed, 22 Jul 2009 02:47:03 +0000
Subject: Re: [PATCH] Add fc_id, which gives ID_PORT_NAME and ID_LUN on appropriate devices.
Message-Id: <200907220647.03748.arvidjaar@mail.ru>
MIME-Version: 1
Content-Type: multipart/mixed; boundary="nextPart5821759.d0SledtzSe"
List-Id: <linux-hotplug.vger.kernel.org>
References: <1248203904-6561-1-git-send-email-pjones@redhat.com>
In-Reply-To: <1248203904-6561-1-git-send-email-pjones@redhat.com>
To: linux-hotplug@vger.kernel.org

--nextPart5821759.d0SledtzSe
Content-Type: Text/Plain;
  charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

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=3D%s\n", port);

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

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

--nextPart5821759.d0SledtzSe
Content-Type: application/pgp-signature; name=signature.asc 
Content-Description: This is a digitally signed message part.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEABECAAYFAkpmfacACgkQR6LMutpd94wURACeLOOhkWEpmAaPchCoBCjaWwsC
aPMAnjrltLD1lmaadRAVOZVoMf8r7Q7+
=OXSj
-----END PGP SIGNATURE-----

--nextPart5821759.d0SledtzSe--