From: Bart Van Assche <bart.vanassche@gmail.com>
To: "James E.J. Bottomley" <James.Bottomley@suse.de>
Cc: linux-scsi@vger.kernel.org, Brian King <brking@linux.vnet.ibm.com>
Subject: Re: [PATCH] SCSI/ibmvscsi: fix a typo in a source code comment
Date: Mon, 4 Jan 2010 17:19:09 +0100 [thread overview]
Message-ID: <e2e108261001040819w218b13c1ja7939c6fd3014e1d@mail.gmail.com> (raw)
In-Reply-To: <200912042043.37328.bart.vanassche@gmail.com>
On Fri, Dec 4, 2009 at 8:43 PM, Bart Van Assche
<bart.vanassche@gmail.com> wrote:
> Signed-off-by: Bart Van Assche <bart.vanassche@gmail.com>
>
> diff --git a/drivers/scsi/ibmvscsi/ibmvscsi.c b/drivers/scsi/ibmvscsi/ibmvscsi.c
> index e475b79..e3a18e0 100644
> --- a/drivers/scsi/ibmvscsi/ibmvscsi.c
> +++ b/drivers/scsi/ibmvscsi/ibmvscsi.c
> @@ -40,7 +40,7 @@
> * (CRQ), which is just a buffer of 16 byte entries in the receiver's
> * Senders cannot access the buffer directly, but send messages by
> * making a hypervisor call and passing in the 16 bytes. The hypervisor
> - * puts the message in the next 16 byte space in round-robbin fashion,
> + * puts the message in the next 16 byte space in round-robin fashion,
> * turns on the high order bit of the message (the valid bit), and
> * generates an interrupt to the receiver (if interrupts are turned on.)
> * The receiver just turns off the valid bit when they have copied out
Hello James,
Does anyone have to ack this trivial patch before it can be added to
the scsi-misc-2.6.git repository ?
Bart.
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-01-04 16:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-04 19:43 [PATCH] SCSI/ibmvscsi: fix a typo in a source code comment Bart Van Assche
2010-01-04 16:19 ` Bart Van Assche [this message]
2010-01-04 16:34 ` James Bottomley
2010-01-04 18:57 ` Brian King
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=e2e108261001040819w218b13c1ja7939c6fd3014e1d@mail.gmail.com \
--to=bart.vanassche@gmail.com \
--cc=James.Bottomley@suse.de \
--cc=brking@linux.vnet.ibm.com \
--cc=linux-scsi@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).