From: Grant Likely <grant.likely@secretlab.ca>
To: Paul Gortmaker <paul.gortmaker@windriver.com>
Cc: rob.herring@calxeda.com, linux-next@vger.kernel.org
Subject: Re: linux-next: "spi/devicetree: Move devicetree support code into spi directory" commit
Date: Fri, 13 Apr 2012 10:23:14 -0600 [thread overview]
Message-ID: <20120413162314.868773E0791@localhost> (raw)
In-Reply-To: <20120413145623.GA3898@windriver.com>
On Fri, 13 Apr 2012 10:56:23 -0400, Paul Gortmaker <paul.gortmaker@windriver.com> wrote:
> Hi Grant,
>
> Can you take a look at this failure?
Hi Paul,
Thanks for telling me about this. It's fixed in my tree now.
g.
>
> drivers/spi/spi-fsl-lib.h:56:33: warning: 'struct spi_message' declared inside parameter list
> drivers/spi/spi-fsl-lib.h:56:33: warning: its scope is only this definition or declaration, which is probably not what you want
> drivers/spi/spi-fsl-lib.h:115:64: warning: 'struct spi_message' declared inside parameter list
> drivers/spi/spi-fsl-lib.c: In function 'mpc8xxx_spi_work':
> drivers/spi/spi-fsl-lib.c:68:27: error: dereferencing pointer to incomplete type
>
> Bisect leads me to:
>
> ------------
> 6810d770847c0f24555c13dd80b64fcc30c47ad8 is the first bad commit
> commit 6810d770847c0f24555c13dd80b64fcc30c47ad8
> Author: Grant Likely <grant.likely@secretlab.ca>
> Date: Sat Apr 7 14:16:53 2012 -0600
>
> spi/devicetree: Move devicetree support code into spi directory
> ------------
>
> Failure is in mpc85xx_defconfig.
>
> http://kisskb.ellerman.id.au/kisskb/buildresult/6100610/
>
> Thanks,
> Paul.
>
>
--
Grant Likely, B.Sc, P.Eng.
Secret Lab Technologies,Ltd.
prev parent reply other threads:[~2012-04-13 16:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-13 14:56 linux-next: "spi/devicetree: Move devicetree support code into spi directory" commit Paul Gortmaker
2012-04-13 16:23 ` Grant Likely [this message]
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=20120413162314.868773E0791@localhost \
--to=grant.likely@secretlab.ca \
--cc=linux-next@vger.kernel.org \
--cc=paul.gortmaker@windriver.com \
--cc=rob.herring@calxeda.com \
/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.