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 v6.13
Date: Tue, 26 Nov 2024 10:18:01 +1000 [thread overview]
Message-ID: <81259608-5796-41ab-9832-0c8312e05b46@linux-m68k.org> (raw)
Hi Linus,
Please pull the m68knommu git tree changes for v6.13.
A couple of small fixes. One to fix compilation when including the FEC driver
(for compile testing) but the specific hardware does not have the hardware module.
And another to fix a typo in the config name used in an ifdef.
Regards
Greg
The following changes since commit 2d5404caa8c7bb5c4e0435f94b28834ae5456623:
Linux 6.12-rc7 (2024-11-10 14:19:35 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gerg/m68knommu.git tags/m68knommu-for-v6.13
for you to fetch changes up to 63a24cf8cc330e5a68ebd2e20ae200096974c475:
m68k: coldfire/device.c: only build FEC when HW macros are defined (2024-11-11 08:57:01 +1000)
----------------------------------------------------------------
m68knommu: updates and fixes for v6.13
Fixes include:
. only include FEC platform entries when hardware supports it
. fix typo in ifdef config name
----------------------------------------------------------------
Antonio Quartulli (1):
m68k: coldfire/device.c: only build FEC when HW macros are defined
Jean-Michel Hautbois (1):
m68k: mcfgpio: Fix incorrect register offset for CONFIG_M5441x
arch/m68k/coldfire/device.c | 8 ++++----
arch/m68k/include/asm/mcfgpio.h | 2 +-
2 files changed, 5 insertions(+), 5 deletions(-)
next reply other threads:[~2024-11-26 0:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-26 0:18 Greg Ungerer [this message]
2024-11-26 23:41 ` 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=81259608-5796-41ab-9832-0c8312e05b46@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®