From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: torvalds@linux-foundation.org
Cc: linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] MIPS fixes for v6.4
Date: Sun, 28 May 2023 10:36:33 +0200 [thread overview]
Message-ID: <20230528083633.GA3069@alpha.franken.de> (raw)
The following changes since commit 44c026a73be8038f03dbdeef028b642880cf1511:
Linux 6.4-rc3 (2023-05-21 14:05:48 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/mips/linux.git/ tags/mips-fixes_6.4_1
for you to fetch changes up to 4897a898a216058dec55e5e5902534e6e224fcdf:
mips: Move initrd_start check after initrd address sanitisation. (2023-05-23 11:01:38 +0200)
----------------------------------------------------------------
- fixes to get alchemy platform back in shape
- fix for initrd detection
----------------------------------------------------------------
Liviu Dudau (1):
mips: Move initrd_start check after initrd address sanitisation.
Manuel Lauss (3):
MIPS: unhide PATA_PLATFORM
MIPS: Restore Au1300 support
MIPS: Alchemy: fix dbdma2
arch/mips/Kconfig | 1 +
arch/mips/alchemy/common/dbdma.c | 27 +++++++++++++++------------
arch/mips/kernel/cpu-probe.c | 5 +++++
arch/mips/kernel/setup.c | 9 +++++----
4 files changed, 26 insertions(+), 16 deletions(-)
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
next reply other threads:[~2023-05-28 8:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-28 8:36 Thomas Bogendoerfer [this message]
2023-05-28 11:46 ` [GIT PULL] MIPS fixes for v6.4 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=20230528083633.GA3069@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@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