All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chandru <chandru@in.ibm.com>
To: Simon Horman <horms@verge.net.au>
Cc: Michael Ellerman <michael@ellerman.id.au>,
	Bernhard Walle <bwalle@suse.de>,
	mohan@in.ibm.com, kexec@lists.infradead.org
Subject: Re: [patch] Possible fix for kexec-tools dynamic range allocation
Date: Fri, 23 Jan 2009 17:01:13 +0530	[thread overview]
Message-ID: <4979AA81.8030300@in.ibm.com> (raw)
In-Reply-To: <20090120212959.GA3564@verge.net.au>

Simon Horman wrote:
>
> Does Bernhard's recent patch (sorry that I applied it even though
> it came in after your patch) help this problem?
>
> commit 95c74405638c786bc76fbca5e4e8427dfe26e907
> Author: Bernhard Walle <bwalle@suse.de>
> Date:   Fri Jan 16 19:11:34 2009 +0100
> Subject: Fix memory corruption when using realloc_memory_ranges()
>
>   
'git clone' or 'git pull' isn't showing these patches. The last commit 
that I can see is : 6d4cdf4f94bf7ad2d1752b553ea948385881ff79 and search 
by that commit doesn't yield anything :(.

Thanks,
Chandru

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

  parent reply	other threads:[~2009-01-23 11:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-07  6:01 [patch] Possible fix for kexec-tools dynamic range allocation Michael Ellerman
2009-01-07  6:01 ` Michael Ellerman
2009-01-20 21:30 ` Simon Horman
2009-01-20 21:30   ` Simon Horman
2009-01-21  1:06   ` Michael Ellerman
2009-01-21  1:06     ` Michael Ellerman
2009-01-23 11:31   ` Chandru [this message]
2009-01-25 23:46     ` Simon Horman

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=4979AA81.8030300@in.ibm.com \
    --to=chandru@in.ibm.com \
    --cc=bwalle@suse.de \
    --cc=horms@verge.net.au \
    --cc=kexec@lists.infradead.org \
    --cc=michael@ellerman.id.au \
    --cc=mohan@in.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.