From: Masahiro Yamada <masahiroy@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] Kbuild fixes for v6.3-rc7
Date: Sun, 16 Apr 2023 20:34:10 +0900 [thread overview]
Message-ID: <CAK7LNATfEXPreAvHcLdzBrRX8ucYWM7t4_VxSLTLdcxPxVaU-Q@mail.gmail.com> (raw)
Hello Linus,
Please pull some more Kbuild fixes.
Thank you.
The following changes since commit 7e364e56293bb98cae1b55fd835f5991c4e96e7d:
Linux 6.3-rc5 (2023-04-02 14:29:29 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/masahiroy/linux-kbuild.git
tags/kbuild-fixes-v6.3-3
for you to fetch changes up to 3c65a2704cdd2a0cd0766352e587bae4a6268155:
kbuild: do not create intermediate *.tar for tar packages
(2023-04-16 17:38:41 +0900)
----------------------------------------------------------------
Kbuild fixes for v6.3 (3rd)
- Drop debug info from purgatory objects again
- Document that kernel.org provides prebuilt LLVM toolchains
- Give up handling untracked files for source package builds
- Avoid creating corrupted cpio when KBUILD_BUILD_TIMESTAMP is given
with a pre-epoch data.
- Change panic_show_mem() to a macro to handle variable-length argument
- Compress tarballs on-the-fly again
----------------------------------------------------------------
Alyssa Ross (1):
purgatory: fix disabling debug info
Benjamin Gray (2):
initramfs: Check negative timestamp to prevent broken cpio archive
init/initramfs: Fix argument forwarding to panic() in panic_show_mem()
Masahiro Yamada (4):
kbuild: give up untracked files for source package builds
kbuild: merge cmd_archive_linux and cmd_archive_perf
kbuild: do not create intermediate *.tar for source tarballs
kbuild: do not create intermediate *.tar for tar packages
Nathan Chancellor (1):
Documentation/llvm: Add a note about prebuilt kernel.org toolchains
Documentation/kbuild/llvm.rst | 4 ++
arch/riscv/purgatory/Makefile | 7 +--
arch/x86/purgatory/Makefile | 3 +-
init/initramfs.c | 11 +----
scripts/Makefile.package | 64 ++++++++++++-------------
scripts/package/gen-diff-patch | 62 +++++++++++--------------
scripts/package/mkdebian | 103 +++++++++++++++++++++++------------------
scripts/package/mkspec | 11 +----
usr/gen_init_cpio.c | 12 +++--
9 files changed, 138 insertions(+), 139 deletions(-)
--
Best Regards
Masahiro Yamada
next reply other threads:[~2023-04-16 11:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-16 11:34 Masahiro Yamada [this message]
2023-04-16 17:43 ` pr-tracker-bot
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=CAK7LNATfEXPreAvHcLdzBrRX8ucYWM7t4_VxSLTLdcxPxVaU-Q@mail.gmail.com \
--to=masahiroy@kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/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
all inboxes | Powered by JetHome®