[PATCH v5 05/10] x86, cleanup: use dbgprint_mem_range for memory range debugging

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: [PATCH v5 05/10] x86, cleanup: use dbgprint_mem_range for memory range debugging
From: chaowang@xxxxxxxxxx (WANG Chao)
Date: Fri, 11 Apr 2014 10:11:10 +0800
In-reply-to: <20140411020021.GB5493@dhcp-16-198.nay.redhat.com>
References: <1397121186-9353-1-git-send-email-chaowang@redhat.com> <1397121186-9353-6-git-send-email-chaowang@redhat.com> <20140410201858.GH18298@oranje.fc.hp.com> <20140411020021.GB5493@dhcp-16-198.nay.redhat.com>

On 04/11/14 at 10:00am, Dave Young wrote:
> > Is the definition for dbgprint_mem_range() missing? It was added in patch v4 1/4
> > but I do not see it in this set.
> 
> I think that one has been merged by Simon..

Yes, Simon has picked up this one.

References:
- [PATCH v5 00/10] kexec-tools, x86: E820 memmap pass for kdump
  - From: WANG Chao
- [PATCH v5 05/10] x86, cleanup: use dbgprint_mem_range for memory range debugging
  - From: WANG Chao
- [PATCH v5 05/10] x86, cleanup: use dbgprint_mem_range for memory range debugging
  - From: Linn Crosetto
- [PATCH v5 05/10] x86, cleanup: use dbgprint_mem_range for memory range debugging
  - From: Dave Young

Prev by Date: [PATCH v5 00/10] kexec-tools, x86: E820 memmap pass for kdump
Next by Date: [PATCH v5 00/10] kexec-tools, x86: E820 memmap pass for kdump
Previous by thread: [PATCH v5 05/10] x86, cleanup: use dbgprint_mem_range for memory range debugging
Next by thread: [PATCH v5 06/10] x86, cleanup: increase CRASH_MAX_MEMMAP_NR up to CRASH_MAX_MEMORY_RANGES
Index(es):
- Date
- Thread

[Index of Archives] [LM Sensors] [Linux Sound] [ALSA Users] [ALSA Devel] [Linux Audio Users] [Linux Media] [Kernel] [Gimp] [Yosemite News] [Linux Media]

Powered by Linux