From: Pratyush Anand <panand@redhat.com>
To: Simon Horman <horms@verge.net.au>, Geoff Levand <geoff@infradead.org>
Cc: kexec@lists.infradead.org
Subject: Re: [PATCH RFC 1/6] purgatory: Fix memcmp for src address increment
Date: Wed, 22 Apr 2015 16:49:30 +0530 [thread overview]
Message-ID: <553783C2.3080207@redhat.com> (raw)
In-Reply-To: <20150420002527.GA17827@verge.net.au>
On Monday 20 April 2015 05:55 AM, Simon Horman wrote:
> On Fri, Apr 17, 2015 at 09:55:44AM -0700, Geoff Levand wrote:
>> On Thu, 2015-04-16 at 22:17 +0530, Pratyush Anand wrote:
>>> src addresses are not being incremented, so only first byte is compared
>>> instead of first len bytes.
>>
>> So I guess this means we never really had proper error
>> checking in purgatory... Better merge this one.
>>
>> Acked-by: Geoff Levand <geoff@infradead.org>
>
> Hi Pratyush,
>
> If you'd like me to take this plase repost it with Geoff's Ack
> and without "RFC".
>
It is already now in Geoff's tree so may be I do not resend it.
~Pratyush
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2015-04-22 11:20 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-16 16:47 [PATCH RFC 0/6] Various fixes for purgatory and ARM64 Pratyush Anand
2015-04-16 16:47 ` [PATCH RFC 1/6] purgatory: Fix memcmp for src address increment Pratyush Anand
2015-04-17 16:55 ` Geoff Levand
2015-04-20 0:25 ` Simon Horman
2015-04-22 11:19 ` Pratyush Anand [this message]
2015-04-23 2:23 ` Simon Horman
2015-04-16 16:47 ` [PATCH RFC 2/6] purgatory: No need to sha256 update if ptr->len is zero Pratyush Anand
2015-04-17 16:58 ` Geoff Levand
2015-04-17 23:26 ` Pratyush Anand
2015-04-20 3:01 ` Baoquan He
2015-04-20 3:18 ` Pratyush Anand
2015-04-16 16:47 ` [PATCH RFC 3/6] arm64: allocate memory for other segments after kernel Pratyush Anand
2015-04-17 16:59 ` Geoff Levand
2015-04-20 3:21 ` Baoquan He
2015-04-21 4:19 ` Pratyush Anand
2015-04-21 10:06 ` AKASHI Takahiro
2015-04-22 6:16 ` AKASHI Takahiro
2015-04-16 16:47 ` [PATCH RFC 4/6] arm64: support reuse-cmdline option Pratyush Anand
2015-04-17 17:02 ` Geoff Levand
2015-04-16 16:47 ` [PATCH RFC 5/6] arm64: Add support for binary image Pratyush Anand
2015-04-17 17:07 ` Geoff Levand
2015-04-17 18:00 ` Geoff Levand
2015-04-17 23:27 ` Pratyush Anand
2015-04-20 7:24 ` Baoquan He
2015-04-21 4:42 ` Pratyush Anand
2015-04-22 2:53 ` Baoquan He
2015-04-22 11:19 ` Pratyush Anand
2015-04-16 16:47 ` [PATCH RFC 6/6] arm64: wait for transmit completion before next character transmission Pratyush Anand
2015-04-17 5:36 ` Minfei Huang
2015-04-17 5:37 ` Pratyush Anand
2015-04-20 2:58 ` Baoquan He
2015-04-20 3:34 ` Pratyush Anand
2015-04-17 17:22 ` Geoff Levand
2015-04-17 23:31 ` Pratyush Anand
2015-04-16 23:54 ` [PATCH RFC 0/6] Various fixes for purgatory and ARM64 Simon Horman
2015-04-17 1:27 ` Dave Young
2015-04-17 2:48 ` Pratyush Anand
2015-04-17 17:27 ` Geoff Levand
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=553783C2.3080207@redhat.com \
--to=panand@redhat.com \
--cc=geoff@infradead.org \
--cc=horms@verge.net.au \
--cc=kexec@lists.infradead.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