From: Nishanth Aravamudan <nacc@us.ibm.com>
To: linuxppc-dev@lists.ozlabs.org
Subject: [nacc@us.ibm.com: [PATCH 00/15] ppc iommu cleanups]
Date: Wed, 15 Sep 2010 11:13:07 -0700 [thread overview]
Message-ID: <20100915181307.GA3683@us.ibm.com> (raw)
Clearly need to work on my git-send-mail usage! Apologies...
----- Forwarded message from Nishanth Aravamudan <nacc@us.ibm.com> -----
Date: Wed, 15 Sep 2010 11:05:43 -0700
From: Nishanth Aravamudan <nacc@us.ibm.com>
To: nacc@us.ibm.com
Subject: [PATCH 00/15] ppc iommu cleanups
While working on some upcoming IOMMU-related changes, we found the
following cleanups throughout the ppc code.
Nishanth Aravamudan (15):
ppc: fix return type of BUID_{HI,LO} macros
ppc64: fix dma_iommu_dma_supported compare
ppc64 iommu: fix check for direct DMA support
vio: put device on device_register failure
viobus: free TCE table on device release
pseries/dlpar: use kmemdup
ppc: pci-common cleanup
microblaze: pci-common cleanup
ppc/vio: use dma ops helpers
ppc/pasemi: clean up pasemi iommu table initializations
ppc/cell: beat dma ops cleanup
ppc/dart: iommu table cleanup
ppc/pseries: iommu cleanup
ppc64 iommu: use coherent_dma_mask for alloc_coherent
ppc/vio: ensure dma_coherent_mask is set
arch/microblaze/pci/pci-common.c | 6 ++----
arch/powerpc/include/asm/ppc-pci.h | 4 ++--
arch/powerpc/kernel/dma-iommu.c | 23 ++++++++++++-----------
arch/powerpc/kernel/dma.c | 2 +-
arch/powerpc/kernel/pci-common.c | 4 +---
arch/powerpc/kernel/vio.c | 24 ++++++++++++++++++------
arch/powerpc/platforms/cell/beat_iommu.c | 3 +--
arch/powerpc/platforms/pasemi/iommu.c | 19 +------------------
arch/powerpc/platforms/pseries/dlpar.c | 3 +--
arch/powerpc/platforms/pseries/iommu.c | 9 ++-------
arch/powerpc/sysdev/dart_iommu.c | 18 +-----------------
11 files changed, 42 insertions(+), 73 deletions(-)
---
I used git-send-email for this series, and noticed that
get_maintainer.pl will always pull in LKML to the Cc because of the
following in MAINTAINERS:
THE REST
M: Linus Torvalds <torvalds@linux-foundation.org>
L: linux-kernel@vger.kernel.org
Q: http://patchwork.kernel.org/project/LKML/list/
T: git git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git
S: Buried alive in reporters
F: *
F: */
Is there any way to exclude that in the script that anyone knows of? Or
am I mis-using the script (as the --cc-cmd option to git-send-email).
Thanks,
Nish
----- End forwarded message -----
--
Nishanth Aravamudan <nacc@us.ibm.com>
IBM Linux Technology Center
reply other threads:[~2010-09-15 18:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100915181307.GA3683@us.ibm.com \
--to=nacc@us.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.