linux-kernel - Re: [PATCH 2/3] add-force-of-use-mmconfig.patch

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <44CEE5F7.6050402@ed-soft.at>
Date:	Tue, 01 Aug 2006 07:26:15 +0200
From:	Edgar Hucek <hostmaster@...soft.at>
To:	Andrew Morton <akpm@...l.org>
CC:	linux-kernel@...r.kernel.org, torvalds@...l.org
Subject: Re: [PATCH 2/3] add-force-of-use-mmconfig.patch

Andrew Morton schrieb:
> On Mon, 31 Jul 2006 10:28:14 +0200
> Edgar Hucek <hostmaster@...soft.at> wrote:
> 
>> This Patch add force for mmconfig. On Intel Macs the efi firmaware gives
>> a different memory map then ACPI_MCFG provides. This makes the check wether
>> to use mmconfig or not fail.
> 
> Sorry, you cannot do this.  I already merged this patch into -mm, and
> followed that up with two bugfix patches, both of which you were copied on.
> 
> Now you're sending out the original patch, without the bugfixes which
> Adrian and I prepared.
> 
> If you think these patches should be merged into 2.6.18 at this late a
> stage, please give reasons and if they're agreeable I can send it all to
> Linus.  But sending out known-buggy stuff which has already been fixed
> doesn't help anyone.
> 
> Also, please don't use filenames as patch descriptions.  See section 2 of
> http://www.zip.com.au/~akpm/linux/patches/stuff/tpp.txt.
> 
> Thanks.
> 

I see only one bugfix patch in your patches ( add-force-of-use-mmconfig-fix.patch )
which is now included in this patch.

cu

ED.
-
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/