mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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.14
Date: Mon, 27 Jan 2025 13:13:58 +1000	[thread overview]
Message-ID: <61cd8e02-debb-46d5-a941-c979a4ad65c7@linux-m68k.org> (raw)

Hi Linus,

Please pull the m68knommu git tree changes for v6.14.

Just a single fix to correct the clock rate defined for the internal timer
hardware blocks of the ColdFire 5441x family of SoC devices.

Regards
Greg





The following changes since commit 5bc55a333a2f7316b58edc7573e8e893f7acb532:

   Linux 6.13-rc7 (2025-01-12 14:37:56 -0800)

are available in the Git repository at:

   git://git.kernel.org/pub/scm/linux/kernel/git/gerg/m68knommu.git tags/m68knommu-for-v6.14

for you to fetch changes up to a0a8306c823986c43ea58be13e8b366999a93cb2:

   m68k: coldfire: Use proper clock rate for timers (2025-01-13 08:51:07 +1000)

----------------------------------------------------------------
m68knommu: updates and fixes for v6.14

Fixes include:
. use proper clock rate for ColdFire 5441x platforms

----------------------------------------------------------------
Jean-Michel Hautbois (1):
       m68k: coldfire: Use proper clock rate for timers

  arch/m68k/coldfire/m5441x.c | 20 ++++++++++----------
  1 file changed, 10 insertions(+), 10 deletions(-)

             reply	other threads:[~2025-01-27  3:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-27  3:13 Greg Ungerer [this message]
2025-01-27 17: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=61cd8e02-debb-46d5-a941-c979a4ad65c7@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®