public inbox for linux-m68k@lists.linux-m68k.org
 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.12
Date: Tue, 24 Sep 2024 14:44:18 +1000	[thread overview]
Message-ID: <f9dfef64-a4fe-406c-9daf-1bf46cd23d65@linux-m68k.org> (raw)

Hi Linus,

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

Only a single change, cleaning up white space in debug message.

Regards
Greg




The following changes since commit da3ea35007d0af457a0afc87e84fddaebc4e0b63:

   Linux 6.11-rc7 (2024-09-08 14:50:28 -0700)

are available in the Git repository at:

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

for you to fetch changes up to aa99969ef591ca44cbafb320ceceb106792baee3:

   m68k: remove trailing space after \n newline (2024-09-09 08:33:35 +1000)

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

Fixes include:
. remove trailing space in pr_debug message

----------------------------------------------------------------
Colin Ian King (1):
       m68k: remove trailing space after \n newline

  arch/m68k/kernel/setup_no.c | 2 +-
  1 file changed, 1 insertion(+), 1 deletion(-)

             reply	other threads:[~2024-09-24  4:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-24  4:44 Greg Ungerer [this message]
2024-09-24 18:04 ` [git pull] m68knommu changes for v6.12 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=f9dfef64-a4fe-406c-9daf-1bf46cd23d65@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