From: Johannes Berg <johannes@sipsolutions.net>
To: Anton Ivanov <anton.ivanov@cambridgegreys.com>,
Ignat Korchagin <ignat@cloudflare.com>
Cc: kernel-team <kernel-team@cloudflare.com>,
Richard Weinberger <richard@nod.at>,
Jeff Dike <jdike@addtoit.com>,
linux-um <linux-um@lists.infradead.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Brendan Higgins <brendanhiggins@google.com>
Subject: Re: [PATCH v2 2/3] um: some fixes to build UML with musl
Date: Tue, 14 Jul 2020 18:02:29 +0200 [thread overview]
Message-ID: <54c5ffb6416bf59f2f287762820ce84d8ad9b495.camel@sipsolutions.net> (raw)
In-Reply-To: <72b84dca-e285-bb1f-1b69-5b29c70806d8@cambridgegreys.com>
On Tue, 2020-07-14 at 11:43 +0100, Anton Ivanov wrote:
> Patch is OK with me, should not read patches before the 3rd double espresso next time.
>
> I will +1 it, Richard, Johannes, what do you think?
I got dropped off the list in "The Great Infradead Purge" but I see it
in patchwork ;)
Not sure we should modify cc-can-link.sh without at least CC'ing
Masahiro Yamada?
But yeah, looks fine to me. Not that I have any interest in static
linking.
johannes
_______________________________________________
linux-um mailing list
linux-um@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-um
next prev parent reply other threads:[~2020-07-14 16:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-04 8:52 [PATCH v2 0/3] um: allow static linking for non-glibc libc implementations Ignat Korchagin
2020-07-04 8:52 ` [PATCH v2 1/3] um/kconfig: introduce CC_CAN_LINK_STATIC_NO_RUNTIME_DEPS Ignat Korchagin
2020-07-15 8:38 ` Brendan Higgins
2020-07-04 8:52 ` [PATCH v2 2/3] um: some fixes to build UML with musl Ignat Korchagin
2020-07-14 8:40 ` Anton Ivanov
2020-07-14 10:23 ` Ignat Korchagin
2020-07-14 10:43 ` Anton Ivanov
2020-07-14 16:02 ` Johannes Berg [this message]
2020-07-15 8:47 ` Brendan Higgins
2020-07-04 8:52 ` [PATCH v2 3/3] um: allow static linking for non-glibc implementations Ignat Korchagin
2020-07-15 8:44 ` Brendan Higgins
2020-07-15 9:30 ` Ignat Korchagin
2020-07-15 8:36 ` [PATCH v2 0/3] um: allow static linking for non-glibc libc implementations Brendan Higgins
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=54c5ffb6416bf59f2f287762820ce84d8ad9b495.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=anton.ivanov@cambridgegreys.com \
--cc=brendanhiggins@google.com \
--cc=ignat@cloudflare.com \
--cc=jdike@addtoit.com \
--cc=kernel-team@cloudflare.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-um@lists.infradead.org \
--cc=richard@nod.at \
/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