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.6
Date: Mon, 4 Sep 2023 11:08:06 +1000 [thread overview]
Message-ID: <fe6c0932-ac00-8a81-4eae-8759547ddd1f@linux-m68k.org> (raw)
Hi Linus,
Please pull the m68knommu git tree changes for v6.6.
Two changes, one a trivial white space clean up, the other removes the
unnecessary local pcibios_setup() code.
Regards
Greg
The following changes since commit 706a741595047797872e669b3101429ab8d378ef:
Linux 6.5-rc7 (2023-08-20 15:02:52 +0200)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gerg/m68knommu.git
tags/m68knommu-for-v6.6
for you to fetch changes up to cf18ecd34f71dfd2815046d4c0d7b6439bb0cbde:
m68k: coldfire: dma_timer: ERROR: "foo __init bar" should be "foo
__init bar" (2023-08-21 08:45:36 +1000)
----------------------------------------------------------------
m68knommu: updates and fixes for v6.6
Fixes include:
. white space cleanup in dma code
. removal of unused pcibios_setup() code
----------------------------------------------------------------
Bjorn Helgaas (1):
m68k/pci: Drop useless pcibios_setup()
hexingwei001@208suo.com (1):
m68k: coldfire: dma_timer: ERROR: "foo __init bar" should be "foo
__init bar"
arch/m68k/coldfire/dma_timer.c | 2 +-
arch/m68k/kernel/pcibios.c | 6 ------
2 files changed, 1 insertion(+), 7 deletions(-)
next reply other threads:[~2023-09-04 1:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-04 1:08 Greg Ungerer [this message]
2023-09-04 18:43 ` 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=fe6c0932-ac00-8a81-4eae-8759547ddd1f@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®