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 v6.3-rc5
Date: Sat, 1 Apr 2023 23:42:33 +0900	[thread overview]
Message-ID: <CAK7LNAQEKgqrJNeknymSTsiRBbjoJJjWQ8VJ7ViC2-9Z0Mgpyw@mail.gmail.com> (raw)

Hello Linus,

Please pull some more Kbuild fixes.
Thank you.



The following changes since commit e8d018dd0257f744ca50a729e3d042cf2ec9da65:

  Linux 6.3-rc3 (2023-03-19 13:27:55 -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-2

for you to fetch changes up to fb27e70f6e408dee5d22b083e7a38a59e6118253:

  modpost: Fix processing of CRCs on 32-bit build machines (2023-03-23
15:28:41 +0900)

----------------------------------------------------------------
Kbuild fixes for v6.3 (2nd)

 - Fix linux-headers debian package

 - Fix a merge_config.sh error due to a misspelled variable

 - Fix modversion for 32-bit build machines

----------------------------------------------------------------
Ben Hutchings (1):
      modpost: Fix processing of CRCs on 32-bit build machines

Kevin Locke (1):
      kbuild: deb-pkg: set version for linux-headers paths

Mirsad Goran Todorovac (1):
      scripts: merge_config: Fix typo in variable name.

 scripts/kconfig/merge_config.sh | 2 +-
 scripts/mod/modpost.c           | 2 +-
 scripts/package/builddeb        | 3 ++-
 3 files changed, 4 insertions(+), 3 deletions(-)


-- 
Best Regards
Masahiro Yamada

             reply	other threads:[~2023-04-01 14:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-01 14:42 Masahiro Yamada [this message]
2023-04-01 16:42 ` [GIT PULL] Kbuild fixes for v6.3-rc5 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=CAK7LNAQEKgqrJNeknymSTsiRBbjoJJjWQ8VJ7ViC2-9Z0Mgpyw@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.