From b7c70a33a5c6ad7cc22cc9ff40f46b35aa01b685 Mon Sep 17 00:00:00 2001
From: Michael Witten <mfwitten@gmail.com>
Date: Thu, 25 Aug 2011 18:57:37 +0000
Subject: [PATCH] --- yaml --- r: 275203 b: refs/heads/master c:
 8d36ffae67d89a86e37e7745503743fec1ac695c h: refs/heads/master i:   275201:
 caffd5cdfb26cb4851799aa09212423c20c1ade2   275199:
 cd56b3bbe1d809a8429a28d4e75cef940cb34c41 v: v3

---
 [refs]                               | 2 +-
 trunk/Documentation/DocBook/drm.tmpl | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/[refs] b/[refs]
index e442d19109c8..10c62534fd93 100644
--- a/[refs]
+++ b/[refs]
@@ -1,2 +1,2 @@
 ---
-refs/heads/master: 118bdd70bdd73b08dcc3920fa30a21be5bbbffae
+refs/heads/master: 8d36ffae67d89a86e37e7745503743fec1ac695c
diff --git a/trunk/Documentation/DocBook/drm.tmpl b/trunk/Documentation/DocBook/drm.tmpl
index ce145babef6e..60ddf4be11c7 100644
--- a/trunk/Documentation/DocBook/drm.tmpl
+++ b/trunk/Documentation/DocBook/drm.tmpl
@@ -372,7 +372,7 @@
 	on the PCI device in the ROM BAR.  Note that after the ROM
 	has been mapped and any necessary information has been extracted,
 	it should be unmapped; on many devices, the ROM address decoder is
-	shared with other BARs, so leaving it mapped can cause
+	shared with other BARs, so leaving it mapped could cause
 	undesired behavior like hangs or memory corruption.
 <!--!Fdrivers/pci/rom.c pci_map_rom-->
       </para>