[PATCH 5/6] docbook: fix kernel-api source files

[Randy Dunlap]

From: Randy Dunlap <randy.dunlap@xxxxxxxxxx>

Fix docbook problems in kernel-api.tmpl.
These cause the generated docbook to be incorrect.

Signed-off-by: Randy Dunlap <randy.dunlap@xxxxxxxxxx>
---
 drivers/base/transport_class.c |    4 +---
 drivers/pci/rom.c              |    3 +--
 mm/truncate.c                  |    3 +--
 3 files changed, 3 insertions(+), 7 deletions(-)

--- lin2625-rc3g2-kdoc.orig/drivers/base/transport_class.c
+++ lin2625-rc3g2-kdoc/drivers/base/transport_class.c
@@ -126,9 +126,7 @@ static int transport_setup_classdev(stru
 }
 
 /**
- * transport_setup_device - declare a new dev for transport class association
- *			    but don't make it visible yet.
- *
+ * transport_setup_device - declare a new dev for transport class association but don't make it visible yet.
  * @dev: the generic device representing the entity being added
  *
  * Usually, dev represents some component in the HBA system (either
--- lin2625-rc3g2-kdoc.orig/drivers/pci/rom.c
+++ lin2625-rc3g2-kdoc/drivers/pci/rom.c
@@ -242,8 +242,7 @@ void pci_remove_rom(struct pci_dev *pdev
 #endif  /*  0  */
 
 /**
- * pci_cleanup_rom - internal routine for freeing the ROM copy created
- * by pci_map_rom_copy called from remove.c
+ * pci_cleanup_rom - free the ROM copy created by pci_map_rom_copy
  * @pdev: pointer to pci device struct
  *
  * Free the copied ROM if we allocated one.
--- lin2625-rc3g2-kdoc.orig/mm/truncate.c
+++ lin2625-rc3g2-kdoc/mm/truncate.c
@@ -134,8 +134,7 @@ invalidate_complete_page(struct address_
 }
 
 /**
- * truncate_inode_pages - truncate range of pages specified by start and
- * end byte offsets
+ * truncate_inode_pages - truncate range of pages specified by start & end byte offsets
  * @mapping: mapping to truncate
  * @lstart: offset from which to truncate
  * @lend: offset to which to truncate
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/