From: Ilias Apalodimas <ilias.apalodimas@linaro.org>
To: Simon Glass <sjg@chromium.org>
Cc: Maxim Uvarov <maxim.uvarov@linaro.org>,
u-boot@lists.denx.de, pbrobinson@redhat.com,
joe.hershberger@ni.com, rfried.dev@gmail.com
Subject: Re: [RFC PATCH 1/5] add lwip-external submodule
Date: Wed, 10 May 2023 10:40:18 +0300 [thread overview]
Message-ID: <ZFtKYpBSP0AsI9u0@hera> (raw)
In-Reply-To: <CAPnjgZ06o0jG77pY0Mp1CiQuZNi6KGZ1EfZLBZhEcvvRELNbtA@mail.gmail.com>
Hi Simon,
On Mon, May 08, 2023 at 08:43:14AM -0600, Simon Glass wrote:
> Hi Maxim,
>
> On Fri, 5 May 2023 at 04:50, Maxim Uvarov <maxim.uvarov@linaro.org> wrote:
> >
> > Signed-off-by: Maxim Uvarov <maxim.uvarov@linaro.org>
> > ---
> > .gitmodules | 3 +++
> > lib/lwip/lwip-external | 1 +
> > 2 files changed, 4 insertions(+)
> > create mode 100644 .gitmodules
> > create mode 160000 lib/lwip/lwip-external
> >
>
> Please no submodules. They are such a pain. If we want the code in
> U-Boot, let's put it in U-Boot and upstream our changes as needed.
Can you explain a bit more the pain points you are seeing in u-boot with
submodules? EDK2 does submodules for openSSL and it's quite convenient,
since you dont have to maintain any code, do backports etc. Instead we can
just use upstream projects as-is.
IMHO we should work on having it as an experimental feature in parallel
with the current TCP efforts for a while and have a Kconfig switch. If we
are happy in the long run and the code increase isn't prohibitive, we can
consider switching permanently
Regards
/Ilias
>
> Regards,
> Simon
next prev parent reply other threads:[~2023-05-10 7:40 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-05 10:25 [RFC PATCH 0/5] LWIP stack integration Maxim Uvarov
2023-05-05 10:25 ` [RFC PATCH 1/5] add lwip-external submodule Maxim Uvarov
2023-05-08 14:43 ` Simon Glass
2023-05-10 7:40 ` Ilias Apalodimas [this message]
2023-05-10 14:46 ` Peter Robinson
2023-05-11 13:51 ` Tom Rini
2023-05-11 13:51 ` Tom Rini
2023-05-05 10:25 ` [RFC PATCH 2/5] lib/lwip: compile-in core files Maxim Uvarov
2023-05-05 10:25 ` [RFC PATCH 3/5] add doc/README.lwip Maxim Uvarov
2023-05-11 13:51 ` Tom Rini
2023-05-05 10:25 ` [RFC PATCH 4/5] add doc/README.lwip.size Maxim Uvarov
2023-05-11 13:51 ` Tom Rini
2023-05-05 10:25 ` [RFC PATCH 5/5] lwip: implement wget command from http_client.c example Maxim Uvarov
2023-05-05 10:27 ` [RFC PATCH 0/5] LWIP stack integration Ilias Apalodimas
2023-05-08 21:23 ` Simon Glass
2023-05-11 13:28 ` Maxim Uvarov
2023-05-11 13:52 ` Tom Rini
2023-05-15 15:25 ` Maxim Uvarov
2023-05-15 15:39 ` Tom Rini
2023-05-19 13:17 ` Ilias Apalodimas
2023-05-19 13:52 ` Tom Rini
2023-05-22 9:01 ` Maxim Uvarov
2023-05-22 13:33 ` Ilias Apalodimas
2023-05-22 14:20 ` Tom Rini
2023-05-22 16:40 ` Maxim Uvarov
2023-05-22 21:23 ` Tom Rini
2023-05-24 14:05 ` Maxim Uvarov
2023-05-24 20:18 ` [lwip-devel] " Simon Goldschmidt
2023-06-06 14:33 ` Maxim Uvarov
2023-06-07 9:46 ` Ilias Apalodimas
2023-06-07 12:01 ` Maxim Uvarov
2023-06-11 8:24 ` Simon Glass
2023-06-11 18:34 ` Tom Rini
2023-06-07 20:07 ` Tom Rini
2023-06-08 10:14 ` Maxim Uvarov
2023-06-08 17:52 ` Ilias Apalodimas
2023-06-09 7:37 ` Peter Robinson
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=ZFtKYpBSP0AsI9u0@hera \
--to=ilias.apalodimas@linaro.org \
--cc=joe.hershberger@ni.com \
--cc=maxim.uvarov@linaro.org \
--cc=pbrobinson@redhat.com \
--cc=rfried.dev@gmail.com \
--cc=sjg@chromium.org \
--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