From: Chris Ball <cjb@laptop.org>
To: Yuvaraj Kumar <yuvaraj.cd@gmail.com>
Cc: Jaehoon Chung <jh80.chung@samsung.com>,
Seungwon Jeon <tgih.jun@samsung.com>,
linux-mmc <linux-mmc@vger.kernel.org>,
thomas.ab@samsung.com, Grant Grundler <grundler@chromium.org>,
Doug Anderson <dianders@chromium.org>,
Sonny Rao <sonnyrao@chromium.org>,
Yuvaraj Kumar C D <yuvaraj.cd@samsung.com>
Subject: Re: [PATCH] mmc: dw_mmc: exynos: Revert the sdr_timing assignment
Date: Fri, 08 Nov 2013 14:29:24 -0500 [thread overview]
Message-ID: <87txfmwv3f.fsf@octavius.laptop.org> (raw)
In-Reply-To: <CAKuRcOKti_ET=9gXGH-Jm8=TYnxag5Cu+wBZ9Hr8nMk=JDiKqA@mail.gmail.com> (Yuvaraj Kumar's message of "Mon, 28 Oct 2013 10:48:10 +0530")
Hi Yuvaraj,
On Mon, Oct 28 2013, Yuvaraj Kumar wrote:
> On Sun, Oct 27, 2013 at 8:08 AM, Chris Ball <cjb@laptop.org> wrote:
>> Hi Yuvaraj,
>>
>> On Tue, Oct 22 2013, Yuvaraj Kumar C D wrote:
>>> commit 4ad602c9df1e3b04979c260b5612141b4b892257 was wrongly assigning
>>> ddr_timing value to sdr_timing.This patch fix's this by reverting
>>> the sdr_timing assignment statement to the earlier location.
>>
>> 4ad602c9df1e3 doesn't exist in mainline. Do you mean e6c784eded7b3
>> ("mmc: dw_mmc: exynos: move the exynos private init")?
> Yes Chris, thats the one.
> Do you want me to respin this patch with the updated commit message?
No, that's okay, I fixed it and pushed to mmc-next for 3.13.
Thanks,
- Chris.
--
Chris Ball <cjb@laptop.org> <http://printf.net/>
prev parent reply other threads:[~2013-11-08 19:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-22 9:11 [PATCH] mmc: dw_mmc: exynos: Revert the sdr_timing assignment Yuvaraj Kumar C D
2013-10-22 10:12 ` Jaehoon Chung
2013-10-23 11:27 ` Seungwon Jeon
2013-10-27 2:38 ` Chris Ball
2013-10-28 5:18 ` Yuvaraj Kumar
2013-11-08 19:29 ` Chris Ball [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=87txfmwv3f.fsf@octavius.laptop.org \
--to=cjb@laptop.org \
--cc=dianders@chromium.org \
--cc=grundler@chromium.org \
--cc=jh80.chung@samsung.com \
--cc=linux-mmc@vger.kernel.org \
--cc=sonnyrao@chromium.org \
--cc=tgih.jun@samsung.com \
--cc=thomas.ab@samsung.com \
--cc=yuvaraj.cd@gmail.com \
--cc=yuvaraj.cd@samsung.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