From: Wolfram Sang <wsa@the-dreams.de>
To: Ulf Hansson <ulf.hansson@linaro.org>
Cc: "Eugeniu Rosca" <erosca@de.adit-jv.com>,
"Wolfram Sang" <wsa+renesas@sang-engineering.com>,
"Yoshihiro Shimoda" <yoshihiro.shimoda.uh@renesas.com>,
"Niklas Söderlund" <niklas.soderlund@ragnatech.se>,
"Geert Uytterhoeven" <geert@linux-m68k.org>,
"Simon Horman" <horms+renesas@verge.net.au>,
"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
"Eugeniu Rosca" <roscaeugeniu@gmail.com>,
"Harish Jenny K N" <harish_kandiga@mentor.com>,
"Andrew Gabbasov" <andrew_gabbasov@mentor.com>
Subject: Re: [PATCH] mmc: renesas_sdhi_internal_dmac: Add MMC_CAP_ERASE to Gen3 SoCs
Date: Fri, 15 Nov 2019 11:12:05 +0100 [thread overview]
Message-ID: <20191115101205.GB2227@kunai> (raw)
In-Reply-To: <CAPDyKFpbu0tCWyUHRjVySRF3QR6Hzd8MXA+RhNeCjED1nPtkYg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 196 bytes --]
> I think using a workqueue for scheduling a reset work with a timeout
> of 5 s, as in your case.
Sorry, I didn't get it. You think what exactly? Is it good / bad / ok
for now / ok in general?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-11-15 10:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-12 13:48 [PATCH] mmc: renesas_sdhi_internal_dmac: Add MMC_CAP_ERASE to Gen3 SoCs Eugeniu Rosca
2019-11-12 20:49 ` Wolfram Sang
2019-11-14 10:56 ` Ulf Hansson
2019-11-14 11:37 ` Eugeniu Rosca
2019-11-14 12:48 ` Ulf Hansson
2019-11-14 20:15 ` Wolfram Sang
2019-11-15 9:19 ` Ulf Hansson
2019-11-15 10:12 ` Wolfram Sang [this message]
2019-11-15 10:38 ` Ulf Hansson
2019-11-14 22:07 ` Eugeniu Rosca
2019-11-15 9:27 ` Ulf Hansson
2019-11-15 12:51 ` Eugeniu Rosca
2019-11-15 13:54 ` Eugeniu Rosca
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=20191115101205.GB2227@kunai \
--to=wsa@the-dreams.de \
--cc=andrew_gabbasov@mentor.com \
--cc=erosca@de.adit-jv.com \
--cc=geert@linux-m68k.org \
--cc=harish_kandiga@mentor.com \
--cc=horms+renesas@verge.net.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=niklas.soderlund@ragnatech.se \
--cc=roscaeugeniu@gmail.com \
--cc=ulf.hansson@linaro.org \
--cc=wsa+renesas@sang-engineering.com \
--cc=yoshihiro.shimoda.uh@renesas.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).