From: Tom Rini <trini@konsulko.com>
To: Paul Barker <paul.barker@sancloud.com>
Cc: u-boot@lists.denx.de
Subject: Re: [PATCH 3/3] exports: Fix export of SPI access functions
Date: Wed, 11 May 2022 09:34:33 -0400 [thread overview]
Message-ID: <20220511133433.GQ3901321@bill-the-cat> (raw)
In-Reply-To: <20220505153242.1598807-4-paul.barker@sancloud.com>
[-- Attachment #1: Type: text/plain, Size: 615 bytes --]
On Thu, May 05, 2022 at 03:32:42PM +0000, Paul Barker wrote:
> * With CONFIG_DM_SPI defined, spi_get_bus_and_cs needs to be used
> instead of spi_setup_slave to configure a SPI bus. As spi_setup_slave is
> already present in the export list it is reasonable to also export
> spi_get_bus_and_cs.
>
> * For the functions listed in the jump table to be callable they must
> also be defined in the "exports.h" header. Define the various exported
> SPI functions so that they can be used.
>
> Signed-off-by: Paul Barker <paul.barker@sancloud.com>
Reviewed-by: Tom Rini <trini@konsulko.com>
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2022-05-11 13:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-05 15:32 [PATCH 0/3] Clarify standalone application support Paul Barker
2022-05-05 15:32 ` [PATCH 1/3] Licenses: Clarify exceptions for standalone apps Paul Barker
2022-05-11 13:34 ` Tom Rini
2022-08-26 13:35 ` Wolfgang Denk
2022-10-26 19:26 ` Tom Rini
2022-05-05 15:32 ` [PATCH 2/3] examples: hello_world: Drop inclusion of common header Paul Barker
2022-05-11 13:34 ` Tom Rini
2022-08-26 13:36 ` Wolfgang Denk
2022-10-26 19:26 ` Tom Rini
2022-05-05 15:32 ` [PATCH 3/3] exports: Fix export of SPI access functions Paul Barker
2022-05-11 13:34 ` Tom Rini [this message]
2022-08-26 13:42 ` Wolfgang Denk
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=20220511133433.GQ3901321@bill-the-cat \
--to=trini@konsulko.com \
--cc=paul.barker@sancloud.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;
as well as URLs for NNTP newsgroup(s).