public inbox for llvm@lists.linux.dev
 help / color / mirror / Atom feed
From: Jiri Slaby <jirislaby@kernel.org>
To: Masahiro Yamada <masahiroy@kernel.org>
Cc: Ard Biesheuvel <ardb@kernel.org>,
	linux-kbuild@vger.kernel.org, Michael Matz <matz@suse.de>,
	Kees Cook <keescook@chromium.org>,
	Sami Tolvanen <samitolvanen@google.com>,
	Fangrui Song <maskray@google.com>,
	Michal Marek <michal.lkml@markovi.net>,
	Nathan Chancellor <nathan@kernel.org>,
	Nick Desaulniers <ndesaulniers@google.com>,
	Tom Rix <trix@redhat.com>,
	linux-kernel@vger.kernel.org, llvm@lists.linux.dev
Subject: Re: [RFC PATCH] kbuild: pass objects instead of archives to linker
Date: Mon, 7 Nov 2022 07:12:04 +0100	[thread overview]
Message-ID: <34906659-94df-9de5-dcf7-0e787b7caf17@kernel.org> (raw)
In-Reply-To: <CAK7LNATBuERrR4QvLzDNOw1TVmMP+2J=sJviihBdy8gF=CfA=w@mail.gmail.com>

On 03. 11. 22, 15:47, Masahiro Yamada wrote:
> Can I see your LTO implementation somewhere in public?

Sure:
https://git.kernel.org/pub/scm/linux/kernel/git/jirislaby/linux.git/commit/?h=lto

FWIW, I plan to send a v1 for comments soon as I finished the patch 
order, CCs and commit logs finally.

thanks,
-- 
js
suse labs


  reply	other threads:[~2022-11-07  6:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-02  9:13 [RFC PATCH] kbuild: pass objects instead of archives to linker Masahiro Yamada
2022-11-02  9:21 ` Ard Biesheuvel
2022-11-02  9:44   ` Masahiro Yamada
2022-11-03  7:22     ` Jiri Slaby
2022-11-03 14:47       ` Masahiro Yamada
2022-11-07  6:12         ` Jiri Slaby [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-11-03  5:43 kernel test robot

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=34906659-94df-9de5-dcf7-0e787b7caf17@kernel.org \
    --to=jirislaby@kernel.org \
    --cc=ardb@kernel.org \
    --cc=keescook@chromium.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=llvm@lists.linux.dev \
    --cc=masahiroy@kernel.org \
    --cc=maskray@google.com \
    --cc=matz@suse.de \
    --cc=michal.lkml@markovi.net \
    --cc=nathan@kernel.org \
    --cc=ndesaulniers@google.com \
    --cc=samitolvanen@google.com \
    --cc=trix@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox