From: chris@printf.net (Chris Ball)
To: linux-arm-kernel@lists.infradead.org
Subject: MMC is *still* broken...
Date: Thu, 05 Jun 2014 20:31:56 +0100 [thread overview]
Message-ID: <86oay7noer.fsf@void.printf.net> (raw)
In-Reply-To: <20140605183615.GG23430@n2100.arm.linux.org.uk> (Russell King's message of "Thu, 5 Jun 2014 19:36:15 +0100")
Hi Russell, adding Ulf and Olof,
On Thu, Jun 05 2014, Russell King - ARM Linux wrote:
> drivers/mmc/core/core.c: In function 'mmc_card_power_up':
> drivers/mmc/core/core.c:1517:4: error: implicit declaration of
> function 'gpiod_set_value'
>
> I reported this back in April, and it's still present. This makes me
> wonder if MMC is maintained.... and makes me wonder what the point
> of reporting bugs is if they just get ignored.
I don't recall your report. I might have just failed to read it, but
doing a quick mail search only finds "Subject: randconfig failures -
MMC + trusted foundations" -- which was sent to linux-arm-kernel@, but
not CC'd to linux-mmc@ or to me.
Furthermore, this error does not exist in mmc-next or linux-next,
so it's unclear why or how the MMC maintainers would fix it.
drivers/mmc/core/core.c does not use gpiod_set_value() in these trees.
Presumably you're testing Olof's unmerged patch "mmc: add support for
power-on sequencing through DT". If it needs to include more gpio
headers, that should be reported to Olof for a respin.
The patch has not been merged because we're still discussing the best
way forward on linux-mmc@, in the thread "RFC: representing sdio
devices oob interrupt, clks, etc. in device tree". The most recent
message in the thread is from yesterday.
- Chris.
--
Chris Ball <http://printf.net/>
next prev parent reply other threads:[~2014-06-05 19:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-05 18:36 MMC is *still* broken Russell King - ARM Linux
2014-06-05 19:31 ` Chris Ball [this message]
2014-06-05 22:21 ` Olof Johansson
2014-06-08 9:55 ` Hans de Goede
2014-06-08 11:09 ` Russell King - ARM Linux
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=86oay7noer.fsf@void.printf.net \
--to=chris@printf.net \
--cc=linux-arm-kernel@lists.infradead.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.