linux-mmc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: <wei_wang@realsil.com.cn>
To: cjb@laptop.org, sameo@linux.intel.com
Cc: devel@linuxdriverproject.org, linux-kernel@vger.kernel.org,
	linux-mmc@vger.kernel.org, gregkh@linuxfoundation.org,
	arnd@arndb.de, oakad@yahoo.com, bp@alien8.de,
	Wei WANG <wei_wang@realsil.com.cn>
Subject: [PATCH v4 0/8] rtsx patchset for MFD and MMC tree
Date: Tue, 8 Jan 2013 17:57:21 +0800	[thread overview]
Message-ID: <cover.1357638064.git.wei_wang@realsil.com.cn> (raw)

From: Wei WANG <wei_wang@realsil.com.cn>

v2:
1. Add commit message for patch 2
2. Move pci_set_dma_mask before the pci_enable_device(pcidev) call

v3:
1. Add commit message for patch 3
2. Add patch 8: Use macro defines to replace some variables

v4:
1. Describe why patch 3 is needed
2. Modify a comment character in patch 7

Wei WANG (8):
  MFD:rtsx: Fix typo in comment
  MFD:rtsx: Remove redundant code
  MFD:rtsx: Declare that the DMA address limitation is 32bit explicitly
  MFD:rtsx: Add callback function switch_output_voltage
  MMC:rtsx: Using callback function to switch output voltage
  MFD:rtsx: Add callback function conv_clk_and_div_n
  MFD:rtsx: Fix checkpatch warning
  MFD:rtsx: Use macro defines to replace some variables

 drivers/mfd/rtl8411.c             |   29 ++++++++++++++++++++++++
 drivers/mfd/rts5209.c             |   21 +++++++++++++++++
 drivers/mfd/rts5229.c             |   21 +++++++++++++++++
 drivers/mfd/rtsx_pcr.c            |   45 +++++++++++++++++++++++++------------
 drivers/mfd/rtsx_pcr.h            |    3 +++
 drivers/mmc/host/rtsx_pci_sdmmc.c |   30 +++++--------------------
 include/linux/mfd/rtsx_common.h   |    3 +++
 include/linux/mfd/rtsx_pci.h      |   27 +++++++++++++++++-----
 8 files changed, 135 insertions(+), 44 deletions(-)

-- 
1.7.9.5

             reply	other threads:[~2013-01-08  9:57 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-08  9:57 wei_wang [this message]
2013-01-08  9:57 ` [PATCH v4 1/8] MFD:rtsx: Fix typo in comment wei_wang
2013-01-08  9:57 ` [PATCH v4 2/8] MFD:rtsx: Remove redundant code wei_wang
2013-01-08  9:57 ` [PATCH v4 3/8] MFD:rtsx: Declare that the DMA address limitation is 32bit explicitly wei_wang
2013-01-08  9:57 ` [PATCH v4 4/8] MFD:rtsx: Add callback function switch_output_voltage wei_wang
2013-01-08  9:57 ` [PATCH v4 5/8] MMC:rtsx: Using callback function to switch output voltage wei_wang
2013-01-08  9:57 ` [PATCH v4 6/8] MFD:rtsx: Add callback function conv_clk_and_div_n wei_wang
2013-01-08  9:57 ` [PATCH v4 7/8] MFD:rtsx: Fix checkpatch warning wei_wang
2013-01-08  9:57 ` [PATCH v4 8/8] MFD:rtsx: Use macro defines to replace some variables wei_wang
2013-01-16  9:02 ` [PATCH v4 0/8] rtsx patchset for MFD and MMC tree wwang
2013-01-22  3:31   ` Samuel Ortiz
2013-01-22  3:39     ` wwang
2013-01-22 22:42       ` Samuel Ortiz
2013-01-23  1:23         ` pclinux
2013-01-23  1:32           ` wwang
2013-01-23 15:37             ` Samuel Ortiz
2013-01-23  7:21           ` Dan Carpenter

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=cover.1357638064.git.wei_wang@realsil.com.cn \
    --to=wei_wang@realsil.com.cn \
    --cc=arnd@arndb.de \
    --cc=bp@alien8.de \
    --cc=cjb@laptop.org \
    --cc=devel@linuxdriverproject.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=oakad@yahoo.com \
    --cc=sameo@linux.intel.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).