From: Paul Barker <paul.barker@sancloud.com>
To: u-boot@lists.denx.de
Cc: Paul Barker <paul.barker@sancloud.com>, Wolfgang Denk <wd@denx.de>
Subject: [PATCH 0/3] Clarify standalone application support
Date: Thu, 5 May 2022 15:32:39 +0000 [thread overview]
Message-ID: <20220505153242.1598807-1-paul.barker@sancloud.com> (raw)
While looking into the support for u-boot standalone applications I
noticed that there was some mis-alignment between the license exception
and the files which needed to be included to get a functioning
application. I also noticed that the set of SPI access functions
defined in the jump table was missing a key function and did not match
the set of prototypes defined in the exports header. These patches
should rectify the issues I found.
Paul Barker (3):
Licenses: Clarify exceptions for standalone apps
examples: hello_world: Drop inclusion of common header
exports: Fix export of SPI access functions
Licenses/Exceptions | 12 ++++++++----
examples/standalone/hello_world.c | 1 -
include/_exports.h | 4 ++++
include/exports.h | 15 ++++++++++++++-
4 files changed, 26 insertions(+), 6 deletions(-)
--
2.25.1
next reply other threads:[~2022-05-05 15:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-05 15:32 Paul Barker [this message]
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
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=20220505153242.1598807-1-paul.barker@sancloud.com \
--to=paul.barker@sancloud.com \
--cc=u-boot@lists.denx.de \
--cc=wd@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).