Kexec Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Pratyush Anand <panand@redhat.com>
To: James Morse <james.morse@arm.com>
Cc: geoff@infradead.org, mark.rutland@arm.com, dyoung@redhat.com,
	kexec@lists.infradead.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH V2 0/2] kexec-tools: arm64: Enable D-cache in purgatory
Date: Thu, 23 Feb 2017 11:29:35 +0530	[thread overview]
Message-ID: <611c625e-88a8-b710-4c3a-775718beb86f@redhat.com> (raw)
In-Reply-To: <5874EBAA.2040202@arm.com>

Hi James and all,

Any review comment for patch 2/2?

If no, then I will address comment for 1/2 and will send v3.

~Pratyush

On Tuesday 10 January 2017 07:41 PM, James Morse wrote:
> Hi Pratyush,
>
> On 06/01/17 03:31, Pratyush Anand wrote:
>> Any feedback/review comment on it?
>
> I started going through this last week, I hope to get back to it later this
> week. (I also need to learn/remember how some of the kexec-tools stuff works).
>
>
> Thanks,
>
> James
>
>

_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

      reply	other threads:[~2017-02-23  6:08 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-19  7:13 [PATCH V2 0/2] kexec-tools: arm64: Enable D-cache in purgatory Pratyush Anand
2016-12-19  7:13 ` [PATCH V2 1/2] kexec: arm64: create identity page table to be used " Pratyush Anand
2016-12-19  7:21   ` Maxim Uvarov
2016-12-19  7:23     ` Pratyush Anand
2017-01-17 17:25   ` James Morse
2017-01-18  7:43     ` Pratyush Anand
2017-03-15  9:42       ` Pratyush Anand
2016-12-19  7:13 ` [PATCH V2 2/2] arm64: enable d-cache support during purgatory sha verification Pratyush Anand
2017-01-06  3:31 ` [PATCH V2 0/2] kexec-tools: arm64: Enable D-cache in purgatory Pratyush Anand
2017-01-10 14:11   ` James Morse
2017-02-23  5:59     ` Pratyush Anand [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=611c625e-88a8-b710-4c3a-775718beb86f@redhat.com \
    --to=panand@redhat.com \
    --cc=dyoung@redhat.com \
    --cc=geoff@infradead.org \
    --cc=james.morse@arm.com \
    --cc=kexec@lists.infradead.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=mark.rutland@arm.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