From: Wolfgang Denk <wd@denx.de>
To: Paul Barker <paul.barker@sancloud.com>
Subject: Re: [PATCH 2/3] examples: hello_world: Drop inclusion of common header
Date: Fri, 26 Aug 2022 15:36:09 +0200 [thread overview]
Message-ID: <13110.1661520969@gemini.denx.de> (raw)
In-Reply-To: <20220505153242.1598807-3-paul.barker@sancloud.com>
Dear Paul,
In message <20220505153242.1598807-3-paul.barker@sancloud.com> you wrote:
> The "common.h" header is not covered by the licensing exception for
> standalone applications. Let's drop inclusion of this header from the
> hello_world example to prove that a standalone app can be built without
> it.
>
> Signed-off-by: Paul Barker <paul.barker@sancloud.com>
> ---
> examples/standalone/hello_world.c | 1 -
> 1 file changed, 1 deletion(-)
Acked-off-by: Wolfgang Denk <wd@denx.de>
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr. 5, 82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
An expert is a person who avoids the small errors while sweeping on
to the grand fallacy.
next prev parent reply other threads:[~2022-08-29 7:57 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 [this message]
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=13110.1661520969@gemini.denx.de \
--to=wd@denx.de \
--cc=paul.barker@sancloud.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.