From: Greg Ungerer <gerg@linux-m68k.org>
To: linux-m68k@lists.linux-m68k.org
Cc: geert@linux-m68k.org
Subject: [PATCH 0/7] m68knommu: W=1 fixes
Date: Wed, 13 Sep 2023 23:44:18 +1000 [thread overview]
Message-ID: <20230913134425.2610927-1-gerg@linux-m68k.org> (raw)
As a follow up to Geet's "[PATCH 0/52] m68k: W=1 fixes" series,
https://lore.kernel.org/lkml/cover.1694093327.git.geert@linux-m68k.org/T/ ,
this series adds fixes specific to nommu and ColdFire configurations.
Mostly similar fixes to what Geert had to do, and not too many all up.
Regards
Greg
arch/m68k/68000/ints.c | 5 ++++-
arch/m68k/68000/ints.h | 7 +++++++
arch/m68k/68000/timers.c | 2 ++
arch/m68k/coldfire/intc.c | 4 ++--
arch/m68k/coldfire/vectors.c | 2 ++
arch/m68k/coldfire/vectors.h | 3 +++
arch/m68k/include/asm/mcfgpio.h | 8 ++++----
arch/m68k/kernel/uboot.c | 13 ++++++++-----
arch/m68k/mm/mcfmmu.c | 3 +--
9 files changed, 33 insertions(+), 14 deletions(-)
next reply other threads:[~2023-09-13 13:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-13 13:44 Greg Ungerer [this message]
2023-09-13 13:44 ` [PATCH 1/7] m68knommu: coldfire: add and use "vectors.h" Greg Ungerer
2023-09-13 13:44 ` [PATCH 2/7] m68knommu: coldfire: ensure gpio prototypes visible Greg Ungerer
2023-09-13 13:44 ` [PATCH 3/7] m68knommu: coldfire: make mcf_maskimr() static Greg Ungerer
2023-09-13 13:44 ` [PATCH 4/7] m68knommu: coldfire: fix warnings in uboot argument processing Greg Ungerer
2023-09-13 13:44 ` [PATCH 5/7] m68knommu: coldfire: remove unused variable in MMU code Greg Ungerer
2023-09-13 13:44 ` [PATCH 6/7] m68knommu: 68000: fix warnings in 68000 interrupt handling Greg Ungerer
2023-09-13 13:44 ` [PATCH 7/7] m68knommu: 68000: fix warning in timer code Greg Ungerer
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=20230913134425.2610927-1-gerg@linux-m68k.org \
--to=gerg@linux-m68k.org \
--cc=geert@linux-m68k.org \
--cc=linux-m68k@lists.linux-m68k.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