linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ulf Hansson <ulf.hansson@linaro.org>
To: Linus <torvalds@linux-foundation.org>,
	linux-mmc@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Ulf Hansson <ulf.hansson@linaro.org>
Subject: [GIT PULL] MMC fixes for v5.1-rc5
Date: Fri, 12 Apr 2019 14:02:52 +0200	[thread overview]
Message-ID: <20190412120252.3704-1-ulf.hansson@linaro.org> (raw)

Hi Linus,

Here's a PR with a couple of MMC fixes intended for v5.1-rc5. Details about the
highlights are as usual found in the signed tag.

Please pull this in!

Kind regards
Ulf Hansson


The following changes since commit 8c2ffd9174779014c3fe1f96d9dc3641d9175f00:

  Linux 5.1-rc2 (2019-03-24 14:02:26 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/ulfh/mmc.git tags/mmc-v5.1-rc2

for you to fetch changes up to 5c41ea6d52003b5bc77c2a82fd5ca7d480237d89:

  mmc: sdhci-omap: Don't finish_mrq() on a command error during tuning (2019-04-11 12:40:32 +0200)

----------------------------------------------------------------
MMC host:
 - alcor: Stabilize data write requests
 - sdhci-omap: Fix command error path during tuning

----------------------------------------------------------------
Daniel Drake (1):
      mmc: alcor: don't write data before command has completed

Faiz Abbas (1):
      mmc: sdhci-omap: Don't finish_mrq() on a command error during tuning

 drivers/mmc/host/alcor.c      | 34 +++++++++++++---------------------
 drivers/mmc/host/sdhci-omap.c | 38 ++++++++++++++++++++++++++++++++++++++
 2 files changed, 51 insertions(+), 21 deletions(-)

             reply	other threads:[~2019-04-12 12:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-12 12:02 Ulf Hansson [this message]
2019-04-12 15:30 ` [GIT PULL] MMC fixes for v5.1-rc5 pr-tracker-bot

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=20190412120252.3704-1-ulf.hansson@linaro.org \
    --to=ulf.hansson@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=torvalds@linux-foundation.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 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).