From: sergio.prado@e-labworks.com (Sergio Prado)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v5 2/2] mmc: host: s3cmci: allow probing from device tree
Date: Fri, 31 Mar 2017 19:46:22 -0300 [thread overview]
Message-ID: <20170331224622.GA11126@sprado-desktop> (raw)
In-Reply-To: <CAPDyKFquGSgK7tkYDpkJM7C7JChZMqvmHoJyiLE9_ZG4CGBOSw@mail.gmail.com>
On Fri, Mar 31, 2017 at 01:11:59PM +0200, Ulf Hansson wrote:
> On 31 March 2017 at 09:25, Arnd Bergmann <arnd@arndb.de> wrote:
> > On Sat, Mar 18, 2017 at 2:13 AM, Sergio Prado
> > <sergio.prado@e-labworks.com> wrote:
> >
> >>
> >> +static const struct of_device_id s3cmci_dt_match[] = {
> >> + {
> >> + .compatible = "samsung,s3c2410-sdi",
> >> + .data = (void *)0,
> >> + },
> >> + {
> >> + .compatible = "samsung,s3c2412-sdi",
> >> + .data = (void *)1,
> >> + },
> >> + {
> >> + .compatible = "samsung,s3c2440-sdi",
> >> + .data = (void *)1,
> >> + },
> >> + { /* sentinel */ },
> >> +};
> >> +MODULE_DEVICE_TABLE(of, sdhci_s3c_dt_match);
> >> +
> >
> > The names don't match:
> >
> > In file included from /git/arm-soc/drivers/mmc/host/s3cmci.c:14:0:
> > /git/arm-soc/drivers/mmc/host/s3cmci.c:1844:25: error:
> > 'sdhci_s3c_dt_match' undeclared here (not in a function); did you mean
> > 's3cmci_dt_match'?
> > MODULE_DEVICE_TABLE(of, sdhci_s3c_dt_match);
> > ^
> > /git/arm-soc/include/linux/module.h:212:21: note: in definition of
> > macro 'MODULE_DEVICE_TABLE'
> > extern const typeof(name) __mod_##type##__##name##_device_table \
> > ^~~~
> > /git/arm-soc/include/linux/module.h:212:27: error:
> > '__mod_of__sdhci_s3c_dt_match_device_table' aliased to undefined
> > symbol 'sdhci_s3c_dt_match'
> > extern const typeof(name) __mod_##type##__##name##_device_table \
> > ^
> > /git/arm-soc/drivers/mmc/host/s3cmci.c:1844:1: note: in expansion of
> > macro 'MODULE_DEVICE_TABLE'
> > MODULE_DEVICE_TABLE(of, sdhci_s3c_dt_match);
> > ^~~~~~~~~~~~~~~~~~~
> > /git/arm-soc/scripts/Makefile.build:314: recipe for target
> > 'drivers/mmc/host/s3cmci.o' failed
> >
> > Can you send a fix?
>
> Never mind, I am dropping the patches from my next branch as those
> clearly haven't been built/tested by Sergio properly. It's better that
> he re-spins them.
>
> Arnd, thanks for reporting and even fixing some of the problems!
>
> Kind regards
> Uffe
Arnd, thanks for reporting the error.
I have built/tested the patches, but only as a built-in feature, and
this error occurs when enabled as a module.
I will re-spins them and send v6.
Best regards,
Sergio Prado
next prev parent reply other threads:[~2017-03-31 22:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-18 1:13 [PATCH v5 0/2] mmc: host: s3cmci: add device tree support Sergio Prado
2017-03-18 1:13 ` [PATCH v5 1/2] dt-bindings: mmc: add DT binding for S3C24XX MMC/SD/SDIO controller Sergio Prado
2017-03-18 1:13 ` [PATCH v5 2/2] mmc: host: s3cmci: allow probing from device tree Sergio Prado
2017-03-31 7:25 ` Arnd Bergmann
2017-03-31 11:11 ` Ulf Hansson
2017-03-31 22:46 ` Sergio Prado [this message]
2017-03-24 7:18 ` [PATCH v5 0/2] mmc: host: s3cmci: add device tree support Ulf Hansson
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=20170331224622.GA11126@sprado-desktop \
--to=sergio.prado@e-labworks.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).