From: Kukjin Kim <kgene.kim@samsung.com>
To: 'Mark Brown' <broonie@opensource.wolfsonmicro.com>,
'Sangwook Lee' <sangwook.lee@linaro.org>
Cc: 'Chris Ball' <cjb@laptop.org>, linux-mmc@vger.kernel.org
Subject: RE: Build breakage in sdhci-s3c
Date: Sat, 03 Dec 2011 18:25:03 +0900 [thread overview]
Message-ID: <000101ccb19d$705e45b0$511ad110$%kim@samsung.com> (raw)
In-Reply-To: <20111202130412.GP8245@opensource.wolfsonmicro.com>
Mark Brown wrote:
>
> On Fri, Dec 02, 2011 at 12:59:42PM +0000, Sangwook Lee wrote:
>
> > and I found out that the following patch wasn't applied This patch
> > was acked by you and Thomas.
>
> > http://comments.gmane.org/gmane.linux.kernel.samsung-soc/7832
> > This patch has the title : [PATCH v2 1/2] ARM: SAMSUNG: Add pm_caps
> > into platform data
>
> > Could you help me to solve the below problem ?
>
> Probably the simplest/best solution here is for Chris to apply this
> patch with Kukjin and Thomas' acks to the mmc tree.
Uhm...it is due to late pushing from my local, I need to sort out my tree
now :(
Anyway, Mark's suggestion makes sense, in this case. Because it can be
happened during merge window even though I solve/push it now.
Hi Chris,
Could you please pick up Sangwook Lee's '[PATCH v2 1/2] ARM: SAMSUNG: Add
pm_caps into platform data' with my ack?
If any problems, please let me know.
Thanks.
Best regards,
Kgene.
--
Kukjin Kim <kgene.kim@samsung.com>, Senior Engineer,
SW Solution Development Team, Samsung Electronics Co., Ltd.
prev parent reply other threads:[~2011-12-03 9:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-02 11:58 Build breakage in sdhci-s3c Mark Brown
2011-12-02 12:59 ` Sangwook Lee
2011-12-02 13:04 ` Mark Brown
2011-12-02 13:11 ` Sangwook Lee
2011-12-03 9:25 ` Kukjin Kim [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='000101ccb19d$705e45b0$511ad110$%kim@samsung.com' \
--to=kgene.kim@samsung.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=cjb@laptop.org \
--cc=linux-mmc@vger.kernel.org \
--cc=sangwook.lee@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox