From: Allen Pais <allen.lkml@gmail.com>
To: ludovic.desroches@microchip.com, ulf.hansson@linaro.org,
manuel.lauss@gmail.com, mirq-linux@rere.qmqm.pl,
jh80.chung@samsung.com, oakad@yahoo.com,
yamada.masahiro@socionext.com, brucechang@via.com.tw,
HaraldWelte@viatech.com
Cc: keescook@chromium.org, inux-mmc@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-omap@vger.kernel.org,
Allen Pais <allen.lkml@gmail.com>
Subject: [PATCH 00/10] mmc: convert tasklets to use new tasklet_setup()
Date: Mon, 17 Aug 2020 14:04:58 +0530 [thread overview]
Message-ID: <20200817083508.22657-1-allen.lkml@gmail.com> (raw)
Commit 12cc923f1ccc ("tasklet: Introduce new initialization API")'
introduced a new tasklet initialization API. This series converts
all the mmc drivers to use the new tasklet_setup() API
Allen Pais (10):
mmc: atmel-mci: convert tasklets to use new tasklet_setup() API
mmc: au1xmmc: convert tasklets to use new tasklet_setup() API
mmc: cb710: convert tasklets to use new tasklet_setup() API
mmc: dw_mmc: convert tasklets to use new tasklet_setup() API
mmc: omap: convert tasklets to use new tasklet_setup() API
mmc: renesas: convert tasklets to use new tasklet_setup() API
mmc: s3cmci: convert tasklets to use new tasklet_setup() API
mmc: tifm_sd: convert tasklets to use new tasklet_setup() API
mmc: uniphier: convert tasklets to use new tasklet_setup() API
mmc: via-sdmmc: convert tasklets to use new tasklet_setup() API
drivers/mmc/host/atmel-mci.c | 6 +++---
drivers/mmc/host/au1xmmc.c | 15 ++++++--------
drivers/mmc/host/cb710-mmc.c | 11 +++++-----
drivers/mmc/host/dw_mmc.c | 6 +++---
drivers/mmc/host/omap.c | 7 +++----
drivers/mmc/host/renesas_sdhi.h | 1 +
drivers/mmc/host/renesas_sdhi_core.c | 2 ++
drivers/mmc/host/renesas_sdhi_internal_dmac.c | 20 +++++++++----------
drivers/mmc/host/renesas_sdhi_sys_dmac.c | 9 ++++-----
drivers/mmc/host/s3cmci.c | 6 +++---
drivers/mmc/host/tifm_sd.c | 7 +++----
drivers/mmc/host/uniphier-sd.c | 14 ++++++-------
drivers/mmc/host/via-sdmmc.c | 7 +++----
13 files changed, 53 insertions(+), 58 deletions(-)
--
2.17.1
next reply other threads:[~2020-08-17 8:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-17 8:34 Allen Pais [this message]
2020-08-17 8:34 ` [PATCH 01/10] mmc: atmel-mci: convert tasklets to use new tasklet_setup() API Allen Pais
2020-08-17 8:35 ` [PATCH 02/10] mmc: au1xmmc: " Allen Pais
2020-08-17 8:35 ` [PATCH 03/10] mmc: cb710: " Allen Pais
2020-08-17 8:35 ` [PATCH 04/10] mmc: dw_mmc: " Allen Pais
2020-08-17 8:35 ` [PATCH 05/10] mmc: omap: " Allen Pais
2020-08-17 8:35 ` [PATCH 06/10] mmc: renesas: " Allen Pais
2020-08-17 8:35 ` [PATCH 07/10] mmc: s3cmci: " Allen Pais
2020-08-17 8:35 ` [PATCH 08/10] mmc: tifm_sd: " Allen Pais
2020-08-17 8:35 ` [PATCH 09/10] mmc: uniphier: " Allen Pais
2020-08-17 12:53 ` [PATCH 00/10] mmc: convert tasklets to use new tasklet_setup() Masahiro Yamada
2020-08-17 19:31 ` Kees Cook
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=20200817083508.22657-1-allen.lkml@gmail.com \
--to=allen.lkml@gmail.com \
--cc=HaraldWelte@viatech.com \
--cc=brucechang@via.com.tw \
--cc=inux-mmc@vger.kernel.org \
--cc=jh80.chung@samsung.com \
--cc=keescook@chromium.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=ludovic.desroches@microchip.com \
--cc=manuel.lauss@gmail.com \
--cc=mirq-linux@rere.qmqm.pl \
--cc=oakad@yahoo.com \
--cc=ulf.hansson@linaro.org \
--cc=yamada.masahiro@socionext.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).