The patch titled
     intel_agp: cleanup intel private data (update)
has been added to the -mm tree.  Its filename is
     intel_agp-cleanup-intel-private-data-update.patch

*** Remember to use Documentation/SubmitChecklist when testing your code ***

See http://www.zip.com.au/~akpm/linux/patches/stuff/added-to-mm.txt to find
out what to do about this

------------------------------------------------------
Subject: intel_agp: cleanup intel private data (update)
From: Wang Zhenyu <[EMAIL PROTECTED]>

Remove volatile type declare for IO mem variables.

A single private gart data is used by all drivers, this
makes it clean. Eric Anholt wrote the original patch.

Signed-off-by: Wang Zhenyu <[EMAIL PROTECTED]>
Cc: Dave Jones <[EMAIL PROTECTED]>
Cc: Keith Packard <[EMAIL PROTECTED]>
Cc: Eric Anholt <[EMAIL PROTECTED]>
Signed-off-by: Andrew Morton <[EMAIL PROTECTED]>
---

 drivers/char/agp/intel-agp.c |    4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff -puN 
drivers/char/agp/intel-agp.c~intel_agp-cleanup-intel-private-data-update 
drivers/char/agp/intel-agp.c
--- a/drivers/char/agp/intel-agp.c~intel_agp-cleanup-intel-private-data-update
+++ a/drivers/char/agp/intel-agp.c
@@ -95,8 +95,8 @@ static struct gatt_mask intel_i810_masks
 
 static struct _intel_private {
        struct pci_dev *pcidev; /* device one */
-       volatile u8 __iomem *registers;
-       volatile u32 __iomem *gtt;              /* I915G */
+       u8 __iomem *registers;
+       u32 __iomem *gtt;               /* I915G */
        int num_dcache_entries;
        /* gtt_entries is the number of gtt entries that are already mapped
         * to stolen memory.  Stolen memory is larger than the memory mapped
_

Patches currently in -mm which might be from [EMAIL PROTECTED] are

intel_agp-cleanup-intel-private-data.patch
intel_agp-cleanup-intel-private-data-update.patch
intel_agp-use-table-for-device-probe.patch

-
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to