linux-kernel - Re: [RFC] Using tip.git 'core/resources' as a baseline for a nvdimm.git topic branch

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Fri, 4 Mar 2016 12:14:09 +0100
From:	Ingo Molnar <mingo@...nel.org>
To:	Dan Williams <dan.j.williams@...el.com>
Cc:	Borislav Petkov <bp@...e.de>, Thomas Gleixner <tglx@...utronix.de>,
	"H. Peter Anvin" <hpa@...or.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Toshi Kani <toshi.kani@....com>
Subject: Re: [RFC] Using tip.git 'core/resources' as a baseline for a
 nvdimm.git topic branch


* Dan Williams <dan.j.williams@...el.com> wrote:

> I have nvdimm changes that depend on the re-worked region_intersects()
> routine that is presently located in -tip.  Any objections with me
> using that branch as a baseline for an nvdimm.git topic branch?

No objections from me! To make it easier for you I just refreshed that branch,
to eliminate an upstream conflict, the new base is:

  bc94b99636dc Merge tag 'v4.5-rc6' into core/resources, to resolve conflict

that way you can base your changes on a fairly fresh upstream kernel as well.

There are no regressions in tip:core/resources that I'm aware of.

Thanks,

	Ingo