All of lore.kernel.org
 help / color / mirror / Atom feed
From: Masahiro Yamada <masahiroy@kernel.org>
To: Nick Desaulniers <ndesaulniers@google.com>
Cc: Florian Weimer <fweimer@redhat.com>,
	Arnd Bergmann <arnd@kernel.org>,
	"Jose E. Marchesi" <jemarch@gnu.org>,
	linux-toolchains@vger.kernel.org,
	clang-built-linux <llvm@lists.linux.dev>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: plumbers session on syscall wrapping and kernel header libc circular depdence?
Date: Mon, 25 Apr 2022 13:43:35 +0900	[thread overview]
Message-ID: <CAK7LNARx_z1Cv4YOkYkdbgrv3PKVa3msHh8mCZDFvYDib++4kQ@mail.gmail.com> (raw)
In-Reply-To: <CAKwvOdmwyFDYKMpq0dcvbq06drtZonpNJ3PqLx2RMBE00beHZA@mail.gmail.com>

Hello Nick,

Sorry for the late reply.

On Sat, Apr 16, 2022 at 2:48 AM Nick Desaulniers
<ndesaulniers@google.com> wrote:
>
> Hi Florian, Arnd, and Masahiro,
> Jose and I are currently in the planning process to put together a
> Kernel+Toolchain microconference track at Linux Plumbers Conference
> this year (Sept 12-14) in Dublin, Ireland.
>
> Would you all be interested in a session (if you're planning on
> attending) discussing syscall wrapping for libc's and UAPI circular
> dependency on the libc?
>
> Masahiro and I were recently discussing the feasibility of building
> the kernel UAPI header tests with -nostdinc, but there are some
> interesting complications perhaps worth sharing with others?
> --
> Thanks,
> ~Nick Desaulniers


I am not sure about the travel at the moment.
I may be able to attend it remotely if the the plumbers is held as a
hybrid conference.

I am not quite sure how many developers would be interested in this topic,
but we can continue discussion in the ML as well.

-- 
Best Regards
Masahiro Yamada

  parent reply	other threads:[~2022-04-25  4:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-15 17:48 plumbers session on syscall wrapping and kernel header libc circular depdence? Nick Desaulniers
2022-04-19 10:46 ` Florian Weimer
2022-04-25  4:43 ` Masahiro Yamada [this message]
2022-04-25 17:51   ` Nick Desaulniers

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=CAK7LNARx_z1Cv4YOkYkdbgrv3PKVa3msHh8mCZDFvYDib++4kQ@mail.gmail.com \
    --to=masahiroy@kernel.org \
    --cc=arnd@kernel.org \
    --cc=fweimer@redhat.com \
    --cc=jemarch@gnu.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-toolchains@vger.kernel.org \
    --cc=llvm@lists.linux.dev \
    --cc=ndesaulniers@google.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.