public inbox for linux-mmc@vger.kernel.org
 help / color / mirror / Atom feed
From: Seungwon Jeon <tgih.jun@samsung.com>
To: 'Chris Ball' <cjb@laptop.org>
Cc: linux-mmc@vger.kernel.org, 'Jaehoon Chung' <jh80.chung@samsung.com>
Subject: RE: dw_mmc updates
Date: Mon, 25 Mar 2013 12:08:44 +0900	[thread overview]
Message-ID: <000801ce2906$0fd2aa10$2f77fe30$%jun@samsung.com> (raw)
In-Reply-To: <87boabl5it.fsf@octavius.laptop.org>

Saturday, March 23, 2013, Chris Ball wrote:
> Hi,
> 
> On Thu, Mar 21 2013, Seungwon Jeon wrote:
> > Hi Chris,
> >
> > There are pending patches for dw_mmc a little bit.
> > Please could you pick the following patches to your tree?
> > These patches are sorted and there are currently no conflicts.
> >
> > [PATCH v3] mmc: dw_mmc: read all data in FIFO after Data transfer over
> > interrupt in pio mode
> > [PATCH] mmc: dw-mmc: return the result of mmc_add_host()
> > [PATCH 2/2] mmc: dw_mmc: exynos: Remove unnecessary use of of_match_ptr()
> > [PATCH] mmc: dw_mmc: fixed a wrong UHS_REG 16 bit clear
> > [PATCH v4] mmc: dw_mmc: Add MSHC compatible for Exynos4412
> > [PATCH] mmc: dw_mmc: move host->data_offset init earlier
> > [PATCH] mmc: dw_mmc: setpower on MMC_POWER_{UP,OFF}
> > [PATCH 1/3] dw_mmc: Don't loop when handling an interrupt
> 
> Thanks, I've got all of these (and more) now.
Thank you for taking care of all.

Thanks,
Seungwon Jeon
> 
> - Chris.
> --
> Chris Ball   <cjb@laptop.org>   <http://printf.net/>
> One Laptop Per Child
> --
> To unsubscribe from this list: send the line "unsubscribe linux-mmc" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html


      reply	other threads:[~2013-03-25  3:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-21 12:26 dw_mmc updates Seungwon Jeon
2013-03-22 17:15 ` Chris Ball
2013-03-25  3:08   ` Seungwon Jeon [this message]

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='000801ce2906$0fd2aa10$2f77fe30$%jun@samsung.com' \
    --to=tgih.jun@samsung.com \
    --cc=cjb@laptop.org \
    --cc=jh80.chung@samsung.com \
    --cc=linux-mmc@vger.kernel.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