From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/3] spl: mmc: Fix compiler warning with CONFIG_DM_MMC
Date: Tue, 1 Dec 2015 19:46:51 -0500 [thread overview]
Message-ID: <20151202004651.GO9551@bill-the-cat> (raw)
In-Reply-To: <CAPnjgZ337F5h2n7epQVdYxkOJxvWTHuW8Uim1ZS04hDGpoGhsA@mail.gmail.com>
On Tue, Dec 01, 2015 at 05:33:32PM -0700, Simon Glass wrote:
> Hi Tom,
>
> On 1 December 2015 at 13:19, Tom Rini <trini@konsulko.com> wrote:
> > On Tue, Dec 01, 2015 at 01:01:51PM -0700, Simon Glass wrote:
> >> Hi Nikita,
> >>
> >> On 1 December 2015 at 05:02, Nikita Kiryanov <nikita@compulab.co.il> wrote:
> >> > Hi Simon,
> >> >
> >> > On Mon, Nov 30, 2015 at 10:19:06AM -0700, Simon Glass wrote:
> >> >> Since commit 4188ba3 we get the following warning on rockchip boards:
> >> >>
> >> >> common/spl/spl_mmc.c:111:10: error: 'mmc' undeclared (first use in this function)
> >> >>
> >> >> Correct this by move the variable init earlier.
> >> >
> >> > This looks suspicious. If the problem is that the variable is
> >> > undeclared, the only way to fix it is to declare the variable, which is
> >> > not what this patch does. I would expect this error to persist with
> >> > the patch applied. Also, mmc is clearly declared in the function
> >> > parameter list. It sounds to me like the source of the compile error is
> >> > somewhere earlier in the code.
> >> >
> >>
> >> Well I just tried again and the warning is:
> >>
> >> common/spl/spl_mmc.c: In function ?spl_mmc_load_image?:
> >> common/spl/spl_mmc.c:31:24: warning: ?mmc? may be used uninitialized
> >> in this function [-Wmaybe-uninitialized]
> >> count = mmc->block_dev.block_read(0, sector, 1, header);
> >> ^
> >> common/spl/spl_mmc.c:251:14: note: ?mmc? was declared here
> >> struct mmc *mmc;
> >> ^
> >>
> >> I'll fix the commit message. I'm not sure what I was looking at there...
> >
> > While you're in there, please just change to setting this to NULL in the
> > declaration instead of right above the call.
>
> I don't think I can do this, as it is a parameter to a function call.
Yes you can. I fixed (and lost, blarg, got side-tracked and blew away
my changes) by making the declartion on 251 be initalized to NULL.
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20151201/22da393e/attachment.sig>
next prev parent reply other threads:[~2015-12-02 0:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-30 17:19 [U-Boot] [PATCH 0/3] spl: mmc: Fix warning and unify spl_mmc_find_device() Simon Glass
2015-11-30 17:19 ` [U-Boot] [PATCH 1/3] spl: mmc: Fix compiler warning with CONFIG_DM_MMC Simon Glass
2015-12-01 12:02 ` Nikita Kiryanov
2015-12-01 19:57 ` Tom Rini
2015-12-01 20:01 ` Simon Glass
2015-12-01 20:19 ` Tom Rini
2015-12-02 0:33 ` Simon Glass
2015-12-02 0:46 ` Tom Rini [this message]
2015-11-30 17:19 ` [U-Boot] [PATCH 2/3] spl: mmc: Rename 'mmc' variable to 'mmcp' Simon Glass
2015-12-01 12:10 ` Nikita Kiryanov
2015-11-30 17:19 ` [U-Boot] [PATCH 3/3] spl: mmc: Unify non/driver model spl_mmc_find_device() Simon Glass
2015-12-02 10:22 ` [U-Boot] [PATCH 0/3] spl: mmc: Fix warning and unify spl_mmc_find_device() Michal Simek
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=20151202004651.GO9551@bill-the-cat \
--to=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/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