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.13
Date: Tue, 4 May 2021 10:14:45 +1000 [thread overview]
Message-ID: <b2180862-6e08-d813-ac65-83052f87be1c@linux-m68k.org> (raw)
Hi Linus,
Please pull the m68knommu tree for-next branch.
There is a fix for interrupt number range checking for the ColdFire
SIMR interrupt controller.
The other changes are for the binfmt_flat binary loader. To allow RISC-V
nommu support it needs to be able to accept flat binaries that have no
gap between the text and data sections.
Regards
Greg
The following changes since commit bf05bf16c76bb44ab5156223e1e58e26dfe30a88:
Linux 5.12-rc8 (2021-04-18 14:45:32 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gerg/m68knommu.git tags/m68knommu-for-v5.13
for you to fetch changes up to 6b3788e5fb8041211ac2fa7c818ca9010e976a74:
m68k: coldfire: fix irq ranges (2021-04-23 15:33:40 +1000)
----------------------------------------------------------------
M68knommu fixes include:
. fix interrupt range check for ColdFire SIMR interrupt controller
. add support for gapless sections flat format binary (needed by RISC-V)
----------------------------------------------------------------
Angelo Dureghello (1):
m68k: coldfire: fix irq ranges
Damien Le Moal (2):
binfmt_flat: allow not offsetting data start
riscv: Disable data start offset in flat binaries
arch/m68k/coldfire/intc-simr.c | 12 ++++++------
arch/riscv/Kconfig | 1 +
fs/Kconfig.binfmt | 3 +++
fs/binfmt_flat.c | 18 +++++++++++++-----
4 files changed, 23 insertions(+), 11 deletions(-)
next reply other threads:[~2021-05-04 0:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-04 0:14 Greg Ungerer [this message]
2021-05-04 18:30 ` [git pull] m68knommu changes for v5.13 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=b2180862-6e08-d813-ac65-83052f87be1c@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;
as well as URLs for NNTP newsgroup(s).