All of lore.kernel.org
 help / color / mirror / Atom feed
From: Edgar Hucek <hostmaster@ed-soft.at>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org, torvalds@osdl.org
Subject: Re: [PATCH 2/3] add-force-of-use-mmconfig.patch
Date: Tue, 01 Aug 2006 09:06:32 +0200	[thread overview]
Message-ID: <44CEFD78.6050308@ed-soft.at> (raw)
In-Reply-To: <20060731224608.15b13b59.akpm@osdl.org>

Andrew Morton schrieb:
> On Tue, 01 Aug 2006 07:26:15 +0200
> Edgar Hucek <hostmaster@ed-soft.at> wrote:
> 
>> Andrew Morton schrieb:
>>> On Mon, 31 Jul 2006 10:28:14 +0200
>>> Edgar Hucek <hostmaster@ed-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.
>>
> 
> I presently have
> 
> add-force-of-use-mmconfig.patch
> add-force-of-use-mmconfig-fix.patch
> add-force-of-use-mmconfig-fix-2.patch
> 
> and
> 
> add-efi-e820-memory-mapping-on-x86.patch
> add-efi-e820-memory-mapping-on-x86-tidy.patch
> add-efi-e820-memory-mapping-on-x86-fix.patch
> add-efi-e820-memory-mapping-on-x86-fix-2.patch
> 
> all of which you should have been cc'ed on.
> 
> Anyway, unless there's a rush on this work, please check that everything
> looks OK in -mm as we head into 2.6.19-rc1.
> 

Mea culpa. Looked at the wrong place. I checked the patches in mm and they look ok.

cu

Edgar Hucek


      reply	other threads:[~2006-08-01  7:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-31  8:28 [PATCH 2/3] add-force-of-use-mmconfig.patch Edgar Hucek
2006-08-01  5:18 ` Andrew Morton
2006-08-01  5:26   ` Edgar Hucek
2006-08-01  5:46     ` Andrew Morton
2006-08-01  7:06       ` Edgar Hucek [this message]

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=44CEFD78.6050308@ed-soft.at \
    --to=hostmaster@ed-soft.at \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.