All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Winchester <kjwinchester@gmail.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: venkatesh.pallipadi@intel.com, tglx@linutronix.de, hpa@zytor.com,
	linux-kernel@vger.kernel.org, suresh.b.siddha@intel.com,
	Dave Airlie <airlied@redhat.com>
Subject: Re: [patch 0/6] PAT fixes/cleanup following the pfnmap changes
Date: Wed, 14 Jan 2009 20:02:51 -0400	[thread overview]
Message-ID: <496E7D2B.5070606@gmail.com> (raw)
In-Reply-To: <20090111020508.GA29153@elte.hu>

Ingo Molnar wrote:
> * Kevin Winchester <kjwinchester@gmail.com> wrote:
> 
>> venkatesh.pallipadi@intel.com wrote:
>>> Individual patch header has descriptions.
>>>
>> $ git am Patches
>> Applying: x86 PAT: change track_pfn_vma_new to take pgprot_t pointer param
>> error: patch failed: mm/memory.c:1604
>> error: mm/memory.c: patch does not apply
>> Patch failed at 0001.
>> When you have resolved this problem run "git am --resolved".
>> If you would prefer to skip this patch, instead run "git am --skip".
>> To restore the original branch and stop patching run "git am --abort".
>>
>> These do not apply for me to latest Linus git, which is the tree where I 
>> experienced the problem.  Is there some way to fuzz them to get them to 
>> apply?
> 
> Could you check tip/master:
> 
>   http://people.redhat.com/mingo/tip.git/README
> 
> do you still get the messages? [ Btw., did you also experience any 3D 
> performance problems that are solved via Venki's fixes in tip/master? ]
> 

(I had noted in another email that tip/master still had the problem.)

However, with latest Linus' git tree (2.6.29-rc1-00224-ga652504),
I no longer see the error messages I had noted before.  Instead I now see:

[  475.132031] agpgart-amd64 0000:00:00.0: AGP 3.0 bridge
[  475.132056] agpgart-amd64 0000:00:00.0: putting AGP V3 device into 8x mode
[  475.132123] pci 0000:01:00.0: putting AGP V3 device into 8x mode
[  475.502856] [drm:radeon_do_init_cp] *ERROR* could not find ioremap agp regions!

Is this related?  I added Dave Airlie to the CC since perhaps he would be the one
to ask about it?

Thanks,

-- 
Kevin Winchester



      parent reply	other threads:[~2009-01-15  0:03 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-10  0:13 [patch 0/6] PAT fixes/cleanup following the pfnmap changes venkatesh.pallipadi
2009-01-10  0:13 ` [patch 1/6] x86 PAT: remove PFNMAP type on track_pfn_vma_new() error venkatesh.pallipadi
2009-01-10  0:13 ` [patch 2/6] x86 PAT: consolidate old memtype new memtype check into a function venkatesh.pallipadi
2009-01-10  0:13 ` [patch 3/6] x86 PAT: change track_pfn_vma_new to take pgprot_t pointer param venkatesh.pallipadi
2009-01-10  0:13 ` [patch 4/6] x86 PAT: return compatible mapping to remap_pfn_range callers venkatesh.pallipadi
2009-01-10  0:13 ` [patch 5/6] x86 PAT: ioremap_wc should take resource_size_t parameter venkatesh.pallipadi
2009-01-10  0:13 ` [patch 6/6] x86 PAT: Remove CPA WARN_ON for zero pte venkatesh.pallipadi
2009-01-10 13:02 ` [patch 0/6] PAT fixes/cleanup following the pfnmap changes Kevin Winchester
2009-01-11  2:05   ` Ingo Molnar
2009-01-11 16:59     ` Kevin Winchester
2009-01-15  0:02     ` Kevin Winchester [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=496E7D2B.5070606@gmail.com \
    --to=kjwinchester@gmail.com \
    --cc=airlied@redhat.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=suresh.b.siddha@intel.com \
    --cc=tglx@linutronix.de \
    --cc=venkatesh.pallipadi@intel.com \
    /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.