All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Christie <michaelc@cs.wisc.edu>
To: "Nicholas A. Bellinger" <nab@linux-iscsi.org>
Cc: linux-scsi <linux-scsi@vger.kernel.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	James Bottomley <James.Bottomley@HansenPartnership.com>,
	Christoph Hellwig <hch@lst.de>, Hannes Reinecke <hare@suse.de>,
	FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>,
	Boaz Harrosh <bharrosh@panasas.com>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	Andrew Morton <akpm@linux-foundation.org>,
	Douglas Gilbert <dgilbert@interlog.com>,
	Jesper Juhl <jj@chaosbits.net>
Subject: Re: [RFC-v4 11/12] iscsi-target: Add misc utility and debug logic
Date: Tue, 22 Mar 2011 00:04:31 -0500	[thread overview]
Message-ID: <4D882DDF.3040901@cs.wisc.edu> (raw)
In-Reply-To: <4D881FC0.5080100@cs.wisc.edu>

On 03/21/2011 11:04 PM, Mike Christie wrote:
>> +
>> +void iscsit_ntoa2(unsigned char *buf, u32 ip)
>> +{
>> + memset(buf, 0, 18);
>> + sprintf(buf, "%u.%u.%u.%u", ((ip>> 24)& 0xff), ((ip>> 16)& 0xff),
>> + ((ip>> 8)& 0xff), (ip& 0xff));
>> +}
>
> I think we have a function like this already.
>
>
> If not, I think this should be:
>
> sprintf(buf, "%pI4",
>
> What s up with ipv6 btw? That uses %pI6.
>


>> + if (tpg_np->tpg_np->np_sockaddr.ss_family == AF_INET6) {
>> + ip =&tpg_np->tpg_np->np_ipv6[0];
>
>
> Is ip supposed to be a string with the ip address in it? If so is that
> right? Is np_ipv6 a string with the ip address in human readable format,
> but below np_ipv4 is the integer representation then you convert it.

Ignore those, I see in the other patches it is different. Why is that?

  reply	other threads:[~2011-03-22  5:04 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-20  9:31 [RFC-v4 00/12] iSCSI target v4.1.0-rc1 series for .39-rc1 Nicholas A. Bellinger
2011-03-20  9:31 ` [RFC-v4 01/12] iscsi: Resolve iscsi_proto.h naming conflicts with drivers/target/iscsi Nicholas A. Bellinger
2011-03-20  9:31 ` [RFC-v4 02/12] iscsi-target: Add primary iSCSI request/response state machine logic Nicholas A. Bellinger
2011-03-20  9:31   ` Nicholas A. Bellinger
2011-03-20  9:31 ` [RFC-v4 03/12] iscsi-target: Add TCM v4 compatiable ConfigFS control plane Nicholas A. Bellinger
2011-03-20  9:31   ` Nicholas A. Bellinger
2011-03-20  9:31 ` [RFC-v4 04/12] iscsi-target: Add configfs fabric dependent statistics Nicholas A. Bellinger
2011-03-20  9:31 ` [RFC-v4 05/12] iscsi-target: Add TPG and Device logic Nicholas A. Bellinger
2011-03-20  9:31   ` Nicholas A. Bellinger
2011-03-20  9:31 ` [RFC-v4 06/12] iscsi-target: Add iSCSI Login Negotiation and Parameter logic Nicholas A. Bellinger
2011-03-20  9:31   ` Nicholas A. Bellinger
2011-03-20  9:31 ` [RFC-v4 07/12] iscsi-target: Add CHAP Authentication support using libcrypto Nicholas A. Bellinger
2011-03-20  9:31   ` Nicholas A. Bellinger
2011-03-22  1:05   ` Mike Christie
2011-03-22  1:50     ` Nicholas A. Bellinger
2011-03-20  9:31 ` [RFC-v4 08/12] iscsi-target: Add Sequence/PDU list + DataIN response logic Nicholas A. Bellinger
2011-03-20  9:31   ` Nicholas A. Bellinger
2011-03-20  9:31 ` [RFC-v4 09/12] iscsi-target: Add iSCSI Error Recovery Hierarchy support Nicholas A. Bellinger
2011-03-20  9:31   ` Nicholas A. Bellinger
2011-03-20  9:31 ` [RFC-v4 10/12] iscsi-target: Add support for task management operations Nicholas A. Bellinger
2011-03-20  9:31   ` Nicholas A. Bellinger
2011-03-20  9:31 ` [RFC-v4 11/12] iscsi-target: Add misc utility and debug logic Nicholas A. Bellinger
2011-03-20  9:31   ` Nicholas A. Bellinger
2011-03-22  4:04   ` Mike Christie
2011-03-22  5:04     ` Mike Christie [this message]
2011-03-22 21:35     ` Nicholas A. Bellinger
2011-03-20  9:31 ` [RFC-v4 12/12] iscsi-target: Add Makefile/Kconfig and update TCM top level Nicholas A. Bellinger
2011-03-21 20:54 ` [RFC-v4 00/12] iSCSI target v4.1.0-rc1 series for .39-rc1 Nicholas A. Bellinger
2011-03-21 21:07   ` James Bottomley
2011-03-21 21:06     ` Nicholas A. Bellinger
2011-03-21 21:15       ` James Bottomley
2011-03-21 21:18         ` Nicholas A. Bellinger

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=4D882DDF.3040901@cs.wisc.edu \
    --to=michaelc@cs.wisc.edu \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=akpm@linux-foundation.org \
    --cc=bharrosh@panasas.com \
    --cc=dgilbert@interlog.com \
    --cc=fujita.tomonori@lab.ntt.co.jp \
    --cc=hare@suse.de \
    --cc=hch@lst.de \
    --cc=jj@chaosbits.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=nab@linux-iscsi.org \
    --cc=sfr@canb.auug.org.au \
    /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.