From: Bradley Grove <bgrove@attotech.com>
To: Bradley Grove <linuxdrivers@attotech.com>,
"James E.J. Bottomley" <JBottomley@parallels.com>,
trivial@kernel.org
Cc: Boris Bodemann <bobo.barbarossa@gmail.com>,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel-janitors@vger.kernel.org
Subject: Re: [PATCH 1/1] esas2r: Correct typos of "validate" in a comment
Date: Tue, 02 Dec 2014 14:37:07 -0500 [thread overview]
Message-ID: <547E14E3.1070303@attotech.com> (raw)
In-Reply-To: <54774D8D.2030204@gmail.com>
Acked-by: Bradley Grove <bgrove@attotech.com>
Thanks,
Brad
On 11/27/2014 11:13 AM, Boris Bodemann wrote:
> From: Boris Bodemann <bobo.barbarossa@gmail.com>
>
> Correct typos of "validate" in a comment
>
> Signed-off-by: Boris Bodemann <bobo.barbarossa@gmail.com>
> ---
> diff -up a/drivers/scsi/esas2r/esas2r_flash.c b/drivers/scsi/esas2r/esas2r_flash.c
> --- a/drivers/scsi/esas2r/esas2r_flash.c 2014-11-21 18:24:10.000000000 +0100
> +++ b/drivers/scsi/esas2r/esas2r_flash.c 2014-11-27 14:49:03.029899303 +0100
> @@ -684,9 +684,9 @@ static u16 calc_fi_checksum(struct esas2
> * 1) verify the fi_version is correct
> * 2) verify the checksum of the entire image.
> * 3) validate the adap_typ, action and length fields.
> - * 4) valdiate each component header. check the img_type and
> + * 4) validate each component header. check the img_type and
> * length fields
> - * 5) valdiate each component image. validate signatures and
> + * 5) validate each component image. validate signatures and
> * local checksums
> */
> static bool verify_fi(struct esas2r_adapter *a,
> --
> 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:[~2014-12-02 19:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-27 16:13 [PATCH 1/1] esas2r: Correct typos of "validate" in a comment Boris Bodemann
2014-12-02 19:37 ` Bradley Grove [this message]
2014-12-04 9:23 ` Christoph Hellwig
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=547E14E3.1070303@attotech.com \
--to=bgrove@attotech.com \
--cc=JBottomley@parallels.com \
--cc=bobo.barbarossa@gmail.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linuxdrivers@attotech.com \
--cc=trivial@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).