From: Chris Ball <chris@printf.net>
To: Grant Grundler <grundler@chromium.org>
Cc: "cjb@laptop.org" <cjb@laptop.org>,
Ulf Hansson <ulf.hansson@linaro.org>,
"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
Alex Lemberg <Alex.Lemberg@sandisk.com>,
Avi Shchislowski <Avi.Shchislowski@sandisk.com>,
Olof Johansson <olofj@chromium.org>
Subject: Re: [RFC PATCH 1/1 v7]mmc: Support-FFU-for-eMMC-v5.0
Date: Tue, 01 Jul 2014 01:34:29 +0100 [thread overview]
Message-ID: <868uodnch6.fsf@void.printf.net> (raw)
In-Reply-To: <CANEJEGs2dAA0DSZfwYcV8nZn4Z1+MqAa0bJZocTZT5zjXe_dDQ@mail.gmail.com> (Grant Grundler's message of "Mon, 30 Jun 2014 16:35:05 -0700")
Hi Grant, sorry about the delay.
On Tue, Jul 01 2014, Grant Grundler wrote:
> ping? Another week is past.
>
> I know you guys are busy with other stuff. But please at least publish
> what you think the next steps for this patch are.
>
> This is a critical patch for supporting eMMC products and adding
> additional support for other vendors. I'd like to continue working
> with "upstream" and the lack of response in this case is making this
> unnecessarily difficult.
It's tough to merge a significant patch that you haven't tested and we
haven't tested. We could do it, though -- I'd like to hear what Ulf
thinks. Please could you give a quick explanation of why doing this
in kernel-space makes more sense than using your mmc-utils version?
Thanks,
- Chris.
--
Chris Ball <http://printf.net/>
next prev parent reply other threads:[~2014-07-01 0:34 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-19 8:01 [RFC PATCH 1/1 v7]mmc: Support-FFU-for-eMMC-v5.0 Avi Shchislowski
2014-06-23 17:14 ` Grant Grundler
[not found] ` <CAC1bqKg=qse6MkgYD3bJDcBg0f7eis3dZZ=e3SM7bxE2A-XKPA@mail.gmail.com>
[not found] ` <CAC1bqKh59OTYOPNQqiwpr1c=P+KwCFDf53o_YZWqZ8Gs2VaCfA@mail.gmail.com>
2014-06-24 1:48 ` Fwd: " Hsin-Hsiang Tseng
2014-06-27 18:33 ` Grant Grundler
2014-06-28 13:45 ` Hsin-Hsiang Tseng
2014-06-29 8:46 ` Avi Shchislowski
2014-06-30 23:35 ` Grant Grundler
2014-07-01 0:34 ` Chris Ball [this message]
2014-07-01 6:29 ` Hsin-Hsiang Tseng
2014-07-01 11:39 ` Avi Shchislowski
2014-07-02 20:35 ` Gwendal Grignou
2014-07-03 0:15 ` Gwendal Grignou
2014-07-16 15:54 ` Avi Shchislowski
2014-07-03 12:32 ` Alex Lemberg
2014-07-01 15:47 ` Grant Grundler
2014-07-01 17:07 ` Ulf Hansson
2014-07-09 17:27 ` Grant Grundler
2014-07-10 23:08 ` [PATCH] Fix on top of sandisk patches Gwendal Grignou
2014-07-10 23:40 ` Alex Lemberg
2014-07-10 23:46 ` Gwendal Grignou
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=868uodnch6.fsf@void.printf.net \
--to=chris@printf.net \
--cc=Alex.Lemberg@sandisk.com \
--cc=Avi.Shchislowski@sandisk.com \
--cc=cjb@laptop.org \
--cc=grundler@chromium.org \
--cc=linux-mmc@vger.kernel.org \
--cc=olofj@chromium.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox