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.10
Date: Wed, 19 Jun 2024 13:07:40 +0200 [thread overview]
Message-ID: <ZnK7/CW+hLH3/Hhs@alpha.franken.de> (raw)
The following changes since commit 83a7eefedc9b56fe7bfeff13b6c7356688ffa670:
Linux 6.10-rc3 (2024-06-09 14:19:43 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/mips/linux.git/ tags/mips-fixes_6.10_1
for you to fetch changes up to 6e5aee08bd2517397c9572243a816664f2ead547:
Revert "MIPS: pci: lantiq: restore reset gpio polarity" (2024-06-13 10:17:09 +0200)
----------------------------------------------------------------
- fix for BCM6538 boards
- fix RB532 PCI workaround
----------------------------------------------------------------
Christian Marangi (1):
mips: bmips: BCM6358: make sure CBR is correctly set
Ilpo Järvinen (1):
MIPS: Routerboard 532: Fix vendor retry check code
Martin Schiller (1):
MIPS: pci: lantiq: restore reset gpio polarity
Thomas Bogendoerfer (1):
Revert "MIPS: pci: lantiq: restore reset gpio polarity"
arch/mips/bmips/setup.c | 3 ++-
arch/mips/pci/ops-rc32434.c | 4 ++--
2 files changed, 4 insertions(+), 3 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:[~2024-06-19 11:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-19 11:07 Thomas Bogendoerfer [this message]
2024-06-19 17:33 ` [GIT PULL] MIPS fixes for v6.10 pr-tracker-bot
-- strict thread matches above, loose matches on Subject: below --
2024-06-23 10:09 Thomas Bogendoerfer
2024-06-23 15: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=ZnK7/CW+hLH3/Hhs@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