From: Greg Ungerer <gerg@linux-m68k.org>
To: torvalds@linux-foundation.org
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Linux/m68k <linux-m68k@vger.kernel.org>,
Geert Uytterhoeven <geert@linux-m68k.org>,
gerg@kernel.org
Subject: [git pull] m68knommu changes for v5.16
Date: Thu, 11 Nov 2021 09:49:14 +1000 [thread overview]
Message-ID: <318e7461-6fec-a6ac-5c88-e17b6fb914cc@linux-m68k.org> (raw)
Hi Linus,
Please pull the m68knommu changes for v5.16.
Only 2 changes. One removes the now unused CONFIG_MCPU32 symbol.
The other sets a default for the CONFIG_MEMORY_RESERVE config symbol
(this aids scripting and other automation) so you don't interactively get
asked for a value at configure time.
Regards
Greg
The following changes since commit 3906fe9bb7f1a2c8667ae54e967dc8690824f4ea:
Linux 5.15-rc7 (2021-10-25 11:30:31 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gerg/m68knommu.git tags/m68knommu-for-v5.16
for you to fetch changes up to 6dbe88e93c351a6cf5b7c70850d7a1a7f67d83ab:
m68knommu: Remove MCPU32 config symbol (2021-10-26 08:46:27 +1000)
----------------------------------------------------------------
Fixes include:
. remove unused CONFIG_MCPU32 symbol
. default CONFIG_MEMORY_RESERVE value (for scripting)
----------------------------------------------------------------
Geert Uytterhoeven (1):
m68knommu: Remove MCPU32 config symbol
Randy Dunlap (1):
m68k: set a default value for MEMORY_RESERVE
arch/m68k/Kconfig.cpu | 11 -----------
arch/m68k/Kconfig.machine | 1 +
arch/m68k/include/asm/bitops.h | 2 +-
3 files changed, 2 insertions(+), 12 deletions(-)
next reply other threads:[~2021-11-10 23:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-10 23:49 Greg Ungerer [this message]
2021-11-11 23:09 ` 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=318e7461-6fec-a6ac-5c88-e17b6fb914cc@linux-m68k.org \
--to=gerg@linux-m68k.org \
--cc=geert@linux-m68k.org \
--cc=gerg@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@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®