From: Chris Ball <chris@printf.net>
To: balbi@ti.com
Cc: Jaehoon Chung <jh80.chung@samsung.com>,
tgih.jun@samsung.com, linux-mmc@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Ulf Hansson <ulf.hansson@linaro.org>
Subject: Re: [PATCH] mmc: host: dw: fix possible build error
Date: Mon, 03 Mar 2014 19:01:53 +0000 [thread overview]
Message-ID: <86vbvvqf6m.fsf@void.printf.net> (raw)
In-Reply-To: <20140303180614.GA31301@saruman.home> (Felipe Balbi's message of "Mon, 3 Mar 2014 12:06:14 -0600")
Hi,
On Mon, Mar 03 2014, Felipe Balbi wrote:
>> When you send the patch related with dw_mmc controller, could you use
>> the prefix "mmc: dw_mmc:"? "mmc: dw_mmc: fix possible build error"
>
> sure, no problem. Do I *really* need to resend though ? It's already
> -rc5 and I still don't see this patch merged.
No need to resend, I can fix this up -- pushed to mmc-next, thanks.
- Chris.
--
Chris Ball <chris@printf.net> <http://printf.net/>
WARNING: multiple messages have this Message-ID (diff)
From: Chris Ball <chris@printf.net>
To: <balbi@ti.com>
Cc: Jaehoon Chung <jh80.chung@samsung.com>, <tgih.jun@samsung.com>,
<linux-mmc@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Ulf Hansson <ulf.hansson@linaro.org>
Subject: Re: [PATCH] mmc: host: dw: fix possible build error
Date: Mon, 03 Mar 2014 19:01:53 +0000 [thread overview]
Message-ID: <86vbvvqf6m.fsf@void.printf.net> (raw)
In-Reply-To: <20140303180614.GA31301@saruman.home> (Felipe Balbi's message of "Mon, 3 Mar 2014 12:06:14 -0600")
Hi,
On Mon, Mar 03 2014, Felipe Balbi wrote:
>> When you send the patch related with dw_mmc controller, could you use
>> the prefix "mmc: dw_mmc:"? "mmc: dw_mmc: fix possible build error"
>
> sure, no problem. Do I *really* need to resend though ? It's already
> -rc5 and I still don't see this patch merged.
No need to resend, I can fix this up -- pushed to mmc-next, thanks.
- Chris.
--
Chris Ball <chris@printf.net> <http://printf.net/>
next prev parent reply other threads:[~2014-03-03 19:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-25 14:57 [PATCH] mmc: host: dw: fix possible build error Felipe Balbi
2014-02-25 14:57 ` Felipe Balbi
2014-02-25 22:03 ` Jaehoon Chung
2014-03-03 18:06 ` Felipe Balbi
2014-03-03 18:06 ` Felipe Balbi
2014-03-03 19:01 ` Chris Ball [this message]
2014-03-03 19:01 ` Chris Ball
2014-03-03 19:05 ` Felipe Balbi
2014-03-03 19:05 ` Felipe Balbi
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=86vbvvqf6m.fsf@void.printf.net \
--to=chris@printf.net \
--cc=balbi@ti.com \
--cc=jh80.chung@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=tgih.jun@samsung.com \
--cc=ulf.hansson@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.