All of lore.kernel.org
 help / color / mirror / Atom feed
From: Masahiro Yamada <masahiroy@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>
Subject: [GIT PULL] Kbuild fixes for v5.11
Date: Mon, 15 Feb 2021 02:02:19 +0900	[thread overview]
Message-ID: <CAK7LNASpVZdyiN4Ug5zujSFnX5OesaVkFX7aP0feZHEF4DVHWQ@mail.gmail.com> (raw)

Hi Linus,

Please pull Kbuild fixes.
Thanks.

The following changes since commit 92bf22614b21a2706f4993b278017e437f7785b3:

  Linux 5.11-rc7 (2021-02-07 13:57:38 -0800)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/masahiroy/linux-kbuild.git
tags/kbuild-fixes-v5.11-3

for you to fetch changes up to fe968c41ac4f4ec9ffe3c4cf16b72285f5e9674f:

  scripts: set proper OpenSSL include dir also for sign-file
(2021-02-15 01:54:11 +0900)

----------------------------------------------------------------
Kbuild fixes for v5.11 (3rd)

 - Fix CONFIG_TRIM_UNUSED_KSYMS build for ppc64

 - Use pkg-config for scripts/sign-file.c CFLAGS

----------------------------------------------------------------
Masahiro Yamada (2):
      kbuild: fix CONFIG_TRIM_UNUSED_KSYMS build for ppc64
      sparc: remove wrong comment from arch/sparc/include/asm/Kbuild

Rolf Eike Beer (1):
      scripts: set proper OpenSSL include dir also for sign-file

 arch/sparc/include/asm/Kbuild | 2 --
 scripts/Makefile              | 1 +
 scripts/gen_autoksyms.sh      | 3 +++
 3 files changed, 4 insertions(+), 2 deletions(-)




-- 
Best Regards
Masahiro Yamada

             reply	other threads:[~2021-02-14 17:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-14 17:02 Masahiro Yamada [this message]
2021-02-14 20:58 ` [GIT PULL] Kbuild fixes for v5.11 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=CAK7LNASpVZdyiN4Ug5zujSFnX5OesaVkFX7aP0feZHEF4DVHWQ@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 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.