From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] spi: omap3: Fix multiple definition of 'priv'
Date: Tue, 15 Mar 2016 14:50:22 -0400 [thread overview]
Message-ID: <20160315185022.GC23166@bill-the-cat> (raw)
In-Reply-To: <1458066393-3606-1-git-send-email-jteki@openedev.com>
On Tue, Mar 15, 2016 at 11:56:33PM +0530, Jagan Teki wrote:
> Global definition of priv seems no-sense to use it
> for non-dm case and pass the pointer to functions
> which are common to both dm and non-dm.
>
> So, fix this by removing omap3_spi_slave from non-dm
> and make visible to omap3_spi_priv for both dm and non-dm.
>
> Cc: Christophe Ricard <christophe-h.ricard@st.com>
> Reported-by: Tom Rini <trini@konsulko.com>
> Signed-off-by: Jagan Teki <jteki@openedev.com>
Applied to u-boot/master, thanks!
--
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/20160315/b536c7af/attachment.sig>
prev parent reply other threads:[~2016-03-15 18:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-15 18:26 [U-Boot] [PATCH] spi: omap3: Fix multiple definition of 'priv' Jagan Teki
2016-03-15 18:33 ` Jagan Teki
2016-03-15 18:50 ` Tom Rini [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=20160315185022.GC23166@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