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.20
Date: Tue, 9 Aug 2022 10:33:27 +1000 [thread overview]
Message-ID: <c42ca36d-3535-bd31-e965-2b86840a03f7@linux-m68k.org> (raw)
Hi Linus,
Please pull the m68knommu changes for v5.20.
Just a few small changes this time. Spelling fix, sparse warning fix and
a fix for compilation with flexcan driver enabled on hardware without that
hardware block.
Regards
Greg
The following changes since commit e0dccc3b76fb35bb257b4118367a883073d7390e:
Linux 5.19-rc8 (2022-07-24 13:26:27 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gerg/m68knommu.git tags/m68knommu-for-v5.20
for you to fetch changes up to 472e68df4a5eacdbe4fd07cffef1b5ffdd95516b:
m68k: Fix syntax errors in comments (2022-07-25 09:01:09 +1000)
----------------------------------------------------------------
Fixes include:
. spelling in comment
. compilation when flexcan driver enabled
. sparse warning
----------------------------------------------------------------
Randy Dunlap (1):
m68k: coldfire/device.c: protect FLEXCAN blocks
Wang Jingjin (1):
m68k: coldfire: make symbol m523x_clk_lookup static
Xiang wangx (1):
m68k: Fix syntax errors in comments
arch/m68k/coldfire/device.c | 6 +++---
arch/m68k/coldfire/intc-2.c | 2 +-
arch/m68k/coldfire/m523x.c | 2 +-
3 files changed, 5 insertions(+), 5 deletions(-)
next reply other threads:[~2022-08-09 0:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-09 0:33 Greg Ungerer [this message]
2022-08-09 17:02 ` [git pull] m68knommu changes for v5.20 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=c42ca36d-3535-bd31-e965-2b86840a03f7@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