From: Ulf Hansson <ulf.hansson@linaro.org>
To: Geliang Tang <geliangtang@163.com>
Cc: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
linux-mmc <linux-mmc@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 4/7] mmc: sh_mmcif: use to_delayed_work
Date: Wed, 27 Jan 2016 15:15:12 +0100 [thread overview]
Message-ID: <CAPDyKFq97KHVdrmwZeASvn1AsjOXfmTbPhXBU9KBV+sJXk0NOA@mail.gmail.com> (raw)
In-Reply-To: <580d73236305b902cbd6fe7b7880d3e6a6d3a382.1451659910.git.geliangtang@163.com>
On 1 January 2016 at 15:59, Geliang Tang <geliangtang@163.com> wrote:
> Use to_delayed_work() instead of open-coding it.
>
> Signed-off-by: Geliang Tang <geliangtang@163.com>
Thanks, applied for next.
Kind regards
Uffe
> ---
> drivers/mmc/host/sh_mmcif.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/mmc/host/sh_mmcif.c b/drivers/mmc/host/sh_mmcif.c
> index 1ca8a13..e0c076a 100644
> --- a/drivers/mmc/host/sh_mmcif.c
> +++ b/drivers/mmc/host/sh_mmcif.c
> @@ -1395,7 +1395,7 @@ static irqreturn_t sh_mmcif_intr(int irq, void *dev_id)
>
> static void sh_mmcif_timeout_work(struct work_struct *work)
> {
> - struct delayed_work *d = container_of(work, struct delayed_work, work);
> + struct delayed_work *d = to_delayed_work(work);
> struct sh_mmcif_host *host = container_of(d, struct sh_mmcif_host, timeout_work);
> struct mmc_request *mrq = host->mrq;
> struct device *dev = sh_mmcif_host_to_dev(host);
> --
> 2.5.0
>
>
next prev parent reply other threads:[~2016-01-27 14:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-01 14:59 [PATCH 1/7] char: xillybus: use to_delayed_work Geliang Tang
2016-01-01 14:59 ` [PATCH 2/7] edac: i5100_edac: " Geliang Tang
2016-01-01 17:35 ` Borislav Petkov
2016-01-01 14:59 ` [PATCH 3/7] input: touchscreen: " Geliang Tang
2016-01-03 5:07 ` Dmitry Torokhov
2016-01-01 14:59 ` [PATCH 4/7] mmc: sh_mmcif: " Geliang Tang
2016-01-27 14:15 ` Ulf Hansson [this message]
2016-01-01 14:59 ` [PATCH 5/7] mmc: usdhi6rol0: " Geliang Tang
2016-01-27 14:15 ` Ulf Hansson
2016-01-01 14:59 ` [PATCH 6/7] power: generic-adc-battery: " Geliang Tang
2016-01-01 14:59 ` [PATCH 7/7] mvsas: " Geliang Tang
2016-01-01 19:47 ` [PATCH 1/7] char: xillybus: " Eli Billauer
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=CAPDyKFq97KHVdrmwZeASvn1AsjOXfmTbPhXBU9KBV+sJXk0NOA@mail.gmail.com \
--to=ulf.hansson@linaro.org \
--cc=geliangtang@163.com \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=linux-kernel@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).