The patch titled mn10300: remove pci_dac_dma_... APIs has been added to the -mm tree. Its filename is mn10300-remove-pci_dac_dma_-apis.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: mn10300: remove pci_dac_dma_... APIs From: Fernando Luis Vazquez Cao <fernando@xxxxxxxxxxxxx> It seems that mn10300 made it upstream after Jan Beulich's pci_dac_dma_* cleanup work and still defines pci_dac_dma_supported(). This API is not required by the PCI subsystem anymore, so remove it. Signed-off-by: Fernando Luis Vazquez Cao <fernando@xxxxxxxxxxxxx> Cc: Jan Beulich <jbeulich@xxxxxxxxxx> Cc: Jesse Barnes <jbarnes@xxxxxxxxxxxxxxxx> Cc: David Howells <dhowells@xxxxxxxxxx> Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> --- include/asm-mn10300/pci.h | 4 ---- 1 file changed, 4 deletions(-) diff -puN include/asm-mn10300/pci.h~mn10300-remove-pci_dac_dma_-apis include/asm-mn10300/pci.h --- a/include/asm-mn10300/pci.h~mn10300-remove-pci_dac_dma_-apis +++ a/include/asm-mn10300/pci.h @@ -70,10 +70,6 @@ struct pci_dev; */ #define PCI_DMA_BUS_IS_PHYS (1) - -/* This is always fine. */ -#define pci_dac_dma_supported(pci_dev, mask) (0) - /* Return the index of the PCI controller for device. */ static inline int pci_controller_num(struct pci_dev *dev) { _ Patches currently in -mm which might be from fernando@xxxxxxxxxxxxx are linux-next.patch mn10300-remove-pci_dac_dma_-apis.patch memcg-do-not-recalculate-section-unnecessarily-in-init_section_page_cgroup.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