From: Mike Christie <michaelc@cs.wisc.edu>
To: Joe Perches <joe@perches.com>
Cc: linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Adaptec OEM Raid Solutions <aacraid@adaptec.com>,
Andrew Vasquez <linux-driver@qlogic.com>,
Brian King <brking@us.ibm.com>,
Dave Jeffery <ipslinux@adaptec.com>,
Hannes Reinecke <hare@suse.de>,
"James E.J. Bottomley" <James.Bottomley@HansenPartnership.com>,
James Smart <james.smart@emulex.com>,
Neela Syam Kolli <megaraidlinux@lsi.com>,
linux-scsi@vger.kernel.org, open-iscsi@googlegroups.com
Subject: Re: [PATCH] drivers/scsi/: Spelling fixes
Date: Mon, 17 Dec 2007 13:58:30 -0600 [thread overview]
Message-ID: <4766D4E6.7000002@cs.wisc.edu> (raw)
In-Reply-To: <1197920439-5455-8-git-send-email-joe@perches.com>
Joe Perches wrote:
> Signed-off-by: Joe Perches <joe@perches.com>
> diff --git a/drivers/scsi/iscsi_tcp.c b/drivers/scsi/iscsi_tcp.c
> index 57ce225..3cc21f5 100644
> --- a/drivers/scsi/iscsi_tcp.c
> +++ b/drivers/scsi/iscsi_tcp.c
> @@ -1121,7 +1121,7 @@ iscsi_send(struct iscsi_conn *conn, struct iscsi_buf *buf, int size, int flags)
> * iscsi_sendhdr - send PDU Header via tcp_sendpage()
> * @conn: iscsi connection
> * @buf: buffer to write from
> - * @datalen: lenght of data to be sent after the header
> + * @datalen: length of data to be sent after the header
> *
> * Notes:
> * (Tx, Fast Path)
> @@ -1724,7 +1724,7 @@ send_hdr:
> * XMSTATE_BIT_SOL_DATA - send solicit data
> *
> *iscsi_tcp_ctask_xmit
> - * XMSTATE_BIT_IMM_DATA - xmit managment data (??)
> + * XMSTATE_BIT_IMM_DATA - xmit management data (??)
> **/
> static int
> iscsi_tcp_ctask_xmit(struct iscsi_conn *conn, struct iscsi_cmd_task *ctask)
Olaf rewrote this code and it will not exist when James merges the
patches, so you can drop the iscsi bits.
next prev parent reply other threads:[~2007-12-17 20:16 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5703e57f925f31fc0eb38873bd7f10fc44f99cb4.1197918893.git.joe@perches.com>
2007-12-17 19:40 ` [PATCH] drivers/scsi/: Spelling fixes Joe Perches
2007-12-17 19:58 ` Mike Christie [this message]
2007-12-17 19:40 ` [PATCH] drivers/serial/: " Joe Perches
2007-12-17 19:40 ` [PATCH] drivers/spi/: " Joe Perches
2007-12-17 19:40 ` [PATCH] drivers/ssb/: " Joe Perches
2007-12-17 19:40 ` [PATCH] drivers/usb/: " Joe Perches
2007-12-17 19:40 ` [PATCH] drivers/video/: " Joe Perches
2007-12-17 19:40 ` [PATCH] drivers/watchdog/: " Joe Perches
2007-12-17 19:40 ` [PATCH] fs/: " Joe Perches
2007-12-17 19:40 ` [PATCH] include/asm-frv/: " Joe Perches
2007-12-17 19:40 ` [PATCH] include/asm-m68knommu/: " Joe Perches
2007-12-24 11:04 ` Greg Ungerer
2007-12-17 19:40 ` [PATCH] include/linux/: " Joe Perches
2007-12-17 21:56 ` [PATCH] drivers/scsi/: " Andrew Vasquez
2007-12-17 22:05 ` James Smart
2007-12-17 22:20 ` [PATCH] include/asm-frv/: " David Howells
2007-12-17 22:48 ` [PATCH] drivers/scsi/: " Darrick J. Wong
2007-12-18 2:27 ` David Somayajulu
2007-12-18 13:55 ` Salyzyn, Mark
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=4766D4E6.7000002@cs.wisc.edu \
--to=michaelc@cs.wisc.edu \
--cc=James.Bottomley@HansenPartnership.com \
--cc=aacraid@adaptec.com \
--cc=akpm@linux-foundation.org \
--cc=brking@us.ibm.com \
--cc=hare@suse.de \
--cc=ipslinux@adaptec.com \
--cc=james.smart@emulex.com \
--cc=joe@perches.com \
--cc=linux-driver@qlogic.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=megaraidlinux@lsi.com \
--cc=open-iscsi@googlegroups.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox