From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Shiji Yang <yangshiji66@outlook.com>
Cc: linux-mips@vger.kernel.org, John Crispin <john@phrozen.org>,
Sergio Paracuellos <sergio.paracuellos@gmail.com>,
Mieczyslaw Nalewaj <namiltd@yahoo.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] MIPS: ralink: some build fixes
Date: Wed, 2 Jul 2025 14:02:12 +0200 [thread overview]
Message-ID: <aGUfxMuvKY_ckBQS@alpha.franken.de> (raw)
In-Reply-To: <OSBPR01MB1670AB9E2C07690BF71FA6F5BC72A@OSBPR01MB1670.jpnprd01.prod.outlook.com>
On Wed, Jun 18, 2025 at 11:40:24PM +0800, Shiji Yang wrote:
> This patch series fixes some MIPS Ralink platform compilation issues
> founded on the OpenWrt distribution 6.12 kernel[1].
>
> [1] https://github.com/openwrt/openwrt/pull/18654
>
> Mieczyslaw Nalewaj (2):
> MIPS: ralink: add missing header include
> MIPS: pci-rt2880: make pcibios_init() static
>
> arch/mips/pci/pci-rt2880.c | 2 +-
> arch/mips/ralink/irq.c | 1 +
> 2 files changed, 2 insertions(+), 1 deletion(-)
series applied to mips-next
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
prev parent reply other threads:[~2025-07-02 13:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-18 15:40 [PATCH 0/2] MIPS: ralink: some build fixes Shiji Yang
2025-06-18 15:40 ` [PATCH 1/2] MIPS: ralink: add missing header include Shiji Yang
2025-06-18 15:40 ` [PATCH 2/2] MIPS: pci-rt2880: make pcibios_init() static Shiji Yang
2025-06-19 4:00 ` [PATCH 0/2] MIPS: ralink: some build fixes Sergio Paracuellos
2025-07-02 12:02 ` Thomas Bogendoerfer [this message]
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=aGUfxMuvKY_ckBQS@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=john@phrozen.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=namiltd@yahoo.com \
--cc=sergio.paracuellos@gmail.com \
--cc=yangshiji66@outlook.com \
/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;
as well as URLs for NNTP newsgroup(s).