From: Simon Horman <horms@verge.net.au>
To: Shailendra Verma <shailendra.capricorn@gmail.com>
Cc: kexec@lists.infradead.org, Eric Biederman <ebiederm@xmission.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kernel:kexec - Fix for typo in comment in function sanity_check_segment_list().
Date: Wed, 2 Sep 2015 10:12:05 +0900 [thread overview]
Message-ID: <20150902011205.GF30886@verge.net.au> (raw)
In-Reply-To: <1432357737-4269-1-git-send-email-shailendra.capricorn@gmail.com>
Hi Shailendra,
On Sat, May 23, 2015 at 10:38:57AM +0530, Shailendra Verma wrote:
>
> Signed-off-by: Shailendra Verma <shailendra.capricorn@gmail.com>
Reviewed-by: Simon Horman <horms@verge.net.au>
I believe if you repost this with Andrew Morton <akpm@linux-foundation.org>
cced then there is a good chance of it progressing into a kernel release.
> ---
> kernel/kexec.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/kernel/kexec.c b/kernel/kexec.c
> index 7a36fdc..50dffdb 100644
> --- a/kernel/kexec.c
> +++ b/kernel/kexec.c
> @@ -189,7 +189,7 @@ static int sanity_check_segment_list(struct kimage *image)
> }
>
> /* Verify our destination addresses do not overlap.
> - * If we alloed overlapping destination addresses
> + * If we allowed overlapping destination addresses
> * through very weird things can happen with no
> * easy explanation as one segment stops on another.
> */
> --
> 1.7.9.5
>
>
> _______________________________________________
> kexec mailing list
> kexec@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/kexec
>
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
prev parent reply other threads:[~2015-09-02 1:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-23 5:08 [PATCH] kernel:kexec - Fix for typo in comment in function sanity_check_segment_list() Shailendra Verma
2015-09-02 1:12 ` Simon Horman [this message]
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=20150902011205.GF30886@verge.net.au \
--to=horms@verge.net.au \
--cc=ebiederm@xmission.com \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shailendra.capricorn@gmail.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