All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jaehoon Chung <jh80.chung@gmail.com>
To: "linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>
Cc: "Ulf Hansson" <ulf.hansson@linaro.org>,
	"Jaehoon Chung" <jh80.chung@samsung.com>,
	"Heiko Stübner" <heiko@sntech.de>,
	"Alexey Brodkin" <Alexey.Brodkin@synopsys.com>,
	"Addy Ke" <addy.ke@rock-chips.com>,
	"Shawn Lin" <shawn.lin@rock-chips.com>
Subject: [GIT PULL] Update dw-mmc controller
Date: Tue, 11 Aug 2015 01:54:21 +0900	[thread overview]
Message-ID: <55C8D73D.10709@gmail.com> (raw)

Dear, Ulf.

Could you pull these patches into your repository?

Best Regards,
Jaehoon Chung

The following changes since commit 77a5f675e2d80469b93c3dea1913c0450c4942be:

  mmc: block: add fixup of broken CMD23 for Sandisk card (2015-07-23 14:28:47 +0200)

are available in the git repository at:

  https://github.com/jh80chung/dw-mmc.git tags/dw-mmc-for-ulf-v4.2

for you to fetch changes up to a4c8b2edf78584dc7148ce06208d0f12d3b04a1b:

  mmc: dw_mmc: add quirk for broken data transfer over scheme (2015-08-11 01:33:32 +0900)

----------------------------------------------------------------
Addy Ke (1):
      mmc: dw_mmc: add quirk for broken data transfer over scheme

Alexey Brodkin (1):
      mmc: dw_mmc: handle data blocks > than 4kB if IDMAC is used

Heiko Stuebner (1):
      mmc: dw_mmc: fix pio mode when internal dmac is enabled

Jaehoon Chung (3):
      mmc: dw_mmc: fix the wrong condition checking
      mmc: dw_mmc: remove the unused blk_setting
      mmc: dw_mmc: print the message for deprecated property

Shawn Lin (1):
      mmc: dw_mmc: Fix coding style issues

 drivers/mmc/host/dw_mmc-rockchip.c |   3 +
 drivers/mmc/host/dw_mmc.c          | 284 +++++++++++++++++++++++++------------
 include/linux/mmc/dw_mmc.h         |   5 +-
 3 files changed, 204 insertions(+), 88 deletions(-)

             reply	other threads:[~2015-08-10 16:54 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-10 16:54 Jaehoon Chung [this message]
2015-08-17  9:47 ` [GIT PULL] Update dw-mmc controller Ulf Hansson
2015-08-17 10:12   ` Alexey Brodkin
2015-08-17 10:32     ` Ulf Hansson
2015-08-17 11:11       ` Alexey Brodkin
2015-09-16 11:27       ` Alexey Brodkin
2015-10-01  9:17         ` Jaehoon Chung
  -- strict thread matches above, loose matches on Subject: below --
2016-10-23 22:52 Jaehoon Chung
2016-10-25  8:48 ` Ulf Hansson
2016-09-22 10:57 Jaehoon Chung
2016-09-22 11:51 ` Ulf Hansson
2016-08-31 10:58 Jaehoon Chung
2016-08-31 11:16 ` Ulf Hansson
2016-06-29  1:42 Jaehoon Chung
2016-07-06 16:19 ` Ulf Hansson
2016-04-06  1:56 Jaehoon Chung
2016-04-06  7:42 ` Ulf Hansson
2016-02-05  2:41 Jaehoon Chung
2016-02-05  7:59 ` Ulf Hansson
2015-10-29  1:46 Jaehoon Chung
2015-10-29 10:03 ` Ulf Hansson
2015-10-21  2:47 Jaehoon Chung
2015-10-21  4:21 ` Jaehoon Chung
2015-10-21  8:38   ` Ulf Hansson
2015-10-21  8:52     ` Jaehoon Chung
2015-06-12  1:54 Jaehoon Chung
2015-06-12  7:33 ` Ulf Hansson
2015-05-18  3:44 Jaehoon Chung
2015-05-18  8:25 ` Ulf Hansson
2015-05-07  8:37 Jaehoon Chung
2015-05-08  7:02 ` Ulf Hansson
2015-05-08  7:06   ` Jaehoon Chung

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=55C8D73D.10709@gmail.com \
    --to=jh80.chung@gmail.com \
    --cc=Alexey.Brodkin@synopsys.com \
    --cc=addy.ke@rock-chips.com \
    --cc=heiko@sntech.de \
    --cc=jh80.chung@samsung.com \
    --cc=linux-mmc@vger.kernel.org \
    --cc=shawn.lin@rock-chips.com \
    --cc=ulf.hansson@linaro.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.