linux-kernel - Re: [PATCH] pci: fix merging left out for BAR print out v2

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:	Thu, 11 Sep 2008 09:43:20 -0700
From:	Jesse Barnes <jbarnes@...tuousgeek.org>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	Yinghai Lu <yhlu.kernel@...il.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	"H. Peter Anvin" <hpa@...or.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org, linux-pci@...ey.karlin.mff.cuni.cz
Subject: Re: [PATCH] pci: fix merging left out for BAR print out v2

On Thursday, September 11, 2008 12:56 am Ingo Molnar wrote:
> > Ah I see, sure I can pull your bits.  /me gets out his breadcrumbs in
> > preparation for entering the x86 forest.  Does your -tip just contain
> > stuff you're sending to Linus for 2.6.27?
>
> no, the .27 buckets of -tip are almost completely emptied - we are in
> the final stages of .27 stabilization. -tip includes all the v2.6.28
> bits. (which this patch would be too IMHO)
>
> anyway, there's no big issue here i think, upstream -git is fine i
> think, please apply the patch to your tree (it only changes printouts),
> it should not cause any big conflicts.

I was thinking it would be good to have this in 2.6.27 since it's a regression 
vs. earlier kernels.  Anyway I'll apply the patch and let git sort out the 
duplication.

Thanks,
-- 
Jesse Barnes, Intel Open Source Technology Center
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/