From: Chris Ball <chris@printf.net>
To: Ulf Hansson <ulf.hansson@linaro.org>
Cc: linux-mmc <linux-mmc@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Russell King <rmk+kernel@arm.linux.org.uk>,
Stephen Warren <swarren@nvidia.com>,
Markus Pargmann <mpa@pengutronix.de>
Subject: Re: [GIT PULL] MMC updates for mmc-next for 3.16, take 3
Date: Thu, 22 May 2014 13:05:16 +0100 [thread overview]
Message-ID: <86zjiaqarn.fsf@void.printf.net> (raw)
In-Reply-To: <CAPDyKFo44fucVebB3f_qby1iWqjyq5P4XPAyD6og5ZWpqgO4=A@mail.gmail.com> (Ulf Hansson's message of "Thu, 22 May 2014 12:49:11 +0200")
Hi Ulf,
On Thu, May 22 2014, Ulf Hansson wrote:
> Here are a third and final collection of patches for 3.16.
>
> I have as you and I discussed (off list), collected the patches from
> Russell's sdhci patchset. I needed to resolve some conflicts while
> applying them, but it was manageable. I also omitted the patch which
> was reported to caused problem with eMMC, (mmc: sdhci: hack up driver
> to make it more compliant with UHS-1).
Pulled, but:
drivers/mmc/host/sdhci.c: In function ‘sdhci_set_uhs_signaling’:
drivers/mmc/host/sdhci.c:1432:12: error: ‘ios’ undeclared (first use
in this function)
else if ((ios->timing == MMC_TIMING_UHS_DDR50) ||
^
drivers/mmc/host/sdhci.c:1432:12: note: each undeclared identifier is
reported only once for each function it appears in
make[3]: *** [drivers/mmc/host/sdhci.o] Error 1
- Chris.
--
Chris Ball <http://printf.net/>
WARNING: multiple messages have this Message-ID (diff)
From: chris@printf.net (Chris Ball)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] MMC updates for mmc-next for 3.16, take 3
Date: Thu, 22 May 2014 13:05:16 +0100 [thread overview]
Message-ID: <86zjiaqarn.fsf@void.printf.net> (raw)
In-Reply-To: <CAPDyKFo44fucVebB3f_qby1iWqjyq5P4XPAyD6og5ZWpqgO4=A@mail.gmail.com> (Ulf Hansson's message of "Thu, 22 May 2014 12:49:11 +0200")
Hi Ulf,
On Thu, May 22 2014, Ulf Hansson wrote:
> Here are a third and final collection of patches for 3.16.
>
> I have as you and I discussed (off list), collected the patches from
> Russell's sdhci patchset. I needed to resolve some conflicts while
> applying them, but it was manageable. I also omitted the patch which
> was reported to caused problem with eMMC, (mmc: sdhci: hack up driver
> to make it more compliant with UHS-1).
Pulled, but:
drivers/mmc/host/sdhci.c: In function ?sdhci_set_uhs_signaling?:
drivers/mmc/host/sdhci.c:1432:12: error: ?ios? undeclared (first use
in this function)
else if ((ios->timing == MMC_TIMING_UHS_DDR50) ||
^
drivers/mmc/host/sdhci.c:1432:12: note: each undeclared identifier is
reported only once for each function it appears in
make[3]: *** [drivers/mmc/host/sdhci.o] Error 1
- Chris.
--
Chris Ball <http://printf.net/>
next prev parent reply other threads:[~2014-05-22 12:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-22 10:49 [GIT PULL] MMC updates for mmc-next for 3.16, take 3 Ulf Hansson
2014-05-22 10:49 ` Ulf Hansson
2014-05-22 12:05 ` Chris Ball [this message]
2014-05-22 12:05 ` Chris Ball
2014-05-22 12:15 ` Ulf Hansson
2014-05-22 12:15 ` Ulf Hansson
2014-05-22 12:34 ` Chris Ball
2014-05-22 12:34 ` Chris Ball
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=86zjiaqarn.fsf@void.printf.net \
--to=chris@printf.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mmc@vger.kernel.org \
--cc=mpa@pengutronix.de \
--cc=rmk+kernel@arm.linux.org.uk \
--cc=swarren@nvidia.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.