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.18
Date: Wed, 23 Mar 2022 15:25:25 +1000 [thread overview]
Message-ID: <472947d1-a827-a490-bd24-6ecb5a762047@linux-m68k.org> (raw)
Hi Linus,
Please pull the m68knommu git tree changes for v5.18.
A few fixes, nothing too exciting. Fix warnings when building for dragen2
targets (sparse and "screen_bits") and ucsimm targets. Fix compilation
problems when test compiling for ColdFire targets with the mcf_edma driver
enabled. Remove an incorrect clock definition for the ColdFire m5441x.
Regards
Greg
The following changes since commit ffb217a13a2eaf6d5bd974fc83036a53ca69f1e2:
Linux 5.17-rc7 (2022-03-06 14:28:31 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gerg/m68knommu.git tags/m68knommu-for-v5.18
for you to fetch changes up to e6e1e7b19fa132d23d09c465942aab4c110d3da9:
m68k: coldfire/device.c: only build for MCF_EDMA when h/w macros are defined (2022-03-07 15:20:16 +1000)
----------------------------------------------------------------
Fixes include:
. fix 'screen_bits' defined but not used
. fix ucsimm sparse warnings
. fix dragen2 warnings
. fix test builds with the mcf_edma driver enabled
----------------------------------------------------------------
Angelo Dureghello (1):
m68k: m5441x: remove erroneous clock disable
Greg Ungerer (3):
m68knommu: fix warning: no previous prototype for 'init_dragen2'
m68knommu: fix 'screen_bits' defined but not used
m68knommu: fix ucsimm sparse warnings
Randy Dunlap (1):
m68k: coldfire/device.c: only build for MCF_EDMA when h/w macros are defined
arch/m68k/68000/dragen2.c | 1 +
arch/m68k/68000/screen.h | 2 ++
arch/m68k/68000/ucsimm.c | 9 ++++-----
arch/m68k/coldfire/device.c | 6 +++---
arch/m68k/coldfire/m5441x.c | 1 -
5 files changed, 10 insertions(+), 9 deletions(-)
next reply other threads:[~2022-03-23 5:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-23 5:25 Greg Ungerer [this message]
2022-03-24 1:00 ` 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=472947d1-a827-a490-bd24-6ecb5a762047@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®