The patch titled pci: fix missing kernel-doc and typos has been added to the -mm tree. Its filename is pci-fix-missing-kernel-doc-and-typos.patch Before you just go and hit "reply", please: a) Consider who else should be cc'ed b) Prefer to cc a suitable mailing list as well c) Ideally: find the original patch on the mailing list and do a reply-to-all to that, adding suitable additional cc's *** Remember to use Documentation/SubmitChecklist when testing your code *** See http://userweb.kernel.org/~akpm/stuff/added-to-mm.txt to find out what to do about this The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/ ------------------------------------------------------ Subject: pci: fix missing kernel-doc and typos From: Randy Dunlap <randy.dunlap@xxxxxxxxxx> Fix pci kernel-doc parameter missing notation, correct function name, and fix typo: Warning(linux-2.6.28-git10//drivers/pci/pci.c:1511): No description found for parameter 'exclusive' Signed-off-by: Randy Dunlap <randy.dunlap@xxxxxxxxxx> Cc: Jesse Barnes <jbarnes@xxxxxxxxxxxxxxxx> Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> --- drivers/pci/pci.c | 13 +++++++++---- 1 file changed, 9 insertions(+), 4 deletions(-) diff -puN drivers/pci/pci.c~pci-fix-missing-kernel-doc-and-typos drivers/pci/pci.c --- a/drivers/pci/pci.c~pci-fix-missing-kernel-doc-and-typos +++ a/drivers/pci/pci.c @@ -1493,16 +1493,21 @@ void pci_release_region(struct pci_dev * } /** - * pci_request_region - Reserved PCI I/O and memory resource + * __pci_request_region - Reserved PCI I/O and memory resource * @pdev: PCI device whose resources are to be reserved * @bar: BAR to be reserved * @res_name: Name to be associated with resource. + * @exclusive: whether the region access is exclusive or not * * Mark the PCI region associated with PCI device @pdev BR @bar as * being reserved by owner @res_name. Do not access any * address inside the PCI regions unless this call returns * successfully. * + * If @exclusive is set, then the region is marked so that userspace + * is explicitly not allowed to map the resource via /dev/mem or + * sysfs MMIO access. + * * Returns 0 on success, or %EBUSY on error. A warning * message is also printed on failure. */ @@ -1541,12 +1546,12 @@ err_out: } /** - * pci_request_region - Reserved PCI I/O and memory resource + * pci_request_region - Reserve PCI I/O and memory resource * @pdev: PCI device whose resources are to be reserved * @bar: BAR to be reserved - * @res_name: Name to be associated with resource. + * @res_name: Name to be associated with resource * - * Mark the PCI region associated with PCI device @pdev BR @bar as + * Mark the PCI region associated with PCI device @pdev BAR @bar as * being reserved by owner @res_name. Do not access any * address inside the PCI regions unless this call returns * successfully. _ Patches currently in -mm which might be from randy.dunlap@xxxxxxxxxx are update-of-documentation-vmtxt-and-proctxt.patch linux-next.patch kgdb-fix-kernel-doc-error.patch auditsc-fix-kernel-doc-notation.patch es-input-allow-certain-ev_abs-events-to-bypass-all-filtering-fix.patch kbuild-fix-kbuildtxt-typos.patch e1000e-make-e1000e-default-to-the-same-kconfig-setting-as-e1000.patch sunrpc-fix-rdma-dependency.patch proc-move-inode-comment-text-file-to-source-file.patch pci-fix-missing-kernel-doc-and-typos.patch esp-fix-section-mismatch-warning.patch libfc-uses-select-crc32.patch sysrq-documentation-remove-the-redundant-updated-date.patch sysrq-documentation-document-why-the-command-header-only-is-shown.patch sysrq-add-commentary-on-why-we-use-the-console-loglevel-over-using-kern_emerg.patch jbd-fix-missing-kernel-doc.patch resources-fix-parameter-name-and-kernel-doc.patch max3100-spi-uart-driver.patch linuxpps-core-support.patch pps-userland-header-file-for-pps-api.patch pps-documentation-programs-and-examples.patch pps-linuxpps-clients-support.patch ldisc-new-dcd_change-method-for-line-disciplines.patch pps-parallel-port-clients-support.patch -- To unsubscribe from this list: send the line "unsubscribe mm-commits" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html