From: Dave Hansen <dave.hansen@intel.com>
To: Lianbo Jiang <lijiang@redhat.com>, linux-kernel@vger.kernel.org
Cc: kexec@lists.infradead.org, x86@kernel.org,
linux-ia64@vger.kernel.org, linux-efi@vger.kernel.org,
tglx@linutronix.de, mingo@redhat.com, bp@alien8.de,
akpm@linux-foundation.org, dave.hansen@linux.intel.com,
luto@kernel.org, peterz@infradead.org, ard.biesheuvel@linaro.org,
tony.luck@intel.com, fenghua.yu@intel.com, dyoung@redhat.com,
bhe@redhat.com
Subject: Re: [PATCH 0/2 RESEND v7] add reserved e820 ranges to the kdump kernel e820 table
Date: Mon, 26 Nov 2018 09:44:46 -0800 [thread overview]
Message-ID: <d457ed46-d983-20b2-ad7f-9eaa6d98f2bf@intel.com> (raw)
In-Reply-To: <20181124051223.19994-1-lijiang@redhat.com>
On 11/23/18 9:12 PM, Lianbo Jiang wrote:
> These patches add the new I/O resource descriptor 'IORES_DESC_RESERVED'
> for the iomem resources search interfaces, and in order to make it still
> work after the new descriptor is added, these codes originally related
> to 'IORES_DESC_NONE' have been updated.
I'm having a really hard time figuring out what problem these patches solve.
What end-user visible behavior does this set change?
next prev parent reply other threads:[~2018-11-26 17:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-24 5:12 [PATCH 0/2 RESEND v7] add reserved e820 ranges to the kdump kernel e820 table Lianbo Jiang
2018-11-24 5:12 ` [PATCH 1/2 RESEND v7] resource: add the new I/O resource descriptor 'IORES_DESC_RESERVED' Lianbo Jiang
2018-11-26 20:52 ` Dave Hansen
2018-11-27 10:04 ` lijiang
2018-11-27 15:34 ` Dave Hansen
2018-11-28 3:51 ` lijiang
2018-11-28 16:02 ` Dave Hansen
2018-11-29 2:14 ` lijiang
2018-11-24 5:12 ` [PATCH 2/2 RESEND v7] x86/kexec_file: add reserved e820 ranges to kdump kernel e820 table Lianbo Jiang
2018-11-26 17:44 ` Dave Hansen [this message]
2018-11-26 18:04 ` [PATCH 0/2 RESEND v7] add reserved e820 ranges to the " Borislav Petkov
2018-11-26 18:54 ` Dave Hansen
2018-11-27 2:58 ` lijiang
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=d457ed46-d983-20b2-ad7f-9eaa6d98f2bf@intel.com \
--to=dave.hansen@intel.com \
--cc=akpm@linux-foundation.org \
--cc=ard.biesheuvel@linaro.org \
--cc=bhe@redhat.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=dyoung@redhat.com \
--cc=fenghua.yu@intel.com \
--cc=kexec@lists.infradead.org \
--cc=lijiang@redhat.com \
--cc=linux-efi@vger.kernel.org \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--cc=x86@kernel.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;
as well as URLs for NNTP newsgroup(s).