All of lore.kernel.org
 help / color / mirror / Atom feed
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 v5.16
Date: Sun, 19 Dec 2021 11:54:55 +0100	[thread overview]
Message-ID: <20211219105455.GA3372@alpha.franken.de> (raw)

The following changes since commit d58071a8a76d779eedab38033ae4c821c30295a5:

  Linux 5.16-rc3 (2021-11-28 14:09:19 -0800)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/mips/linux.git/ tags/mips-fixes_5.16_3

for you to fetch changes up to 09d97da660ff77df20984496aa0abcd6b88819f2:

  MIPS: Only define pci_remap_iospace() for Ralink (2021-12-09 10:22:24 +0100)

----------------------------------------------------------------
- only enable pci_remap_iospace() for Ralink devices

----------------------------------------------------------------
Tiezhu Yang (1):
      MIPS: Only define pci_remap_iospace() for Ralink

 arch/mips/include/asm/mach-ralink/spaces.h | 2 ++
 arch/mips/include/asm/pci.h                | 4 ----
 arch/mips/pci/pci-generic.c                | 2 ++
 3 files changed, 4 insertions(+), 4 deletions(-)

-- 
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea.                                                [ RFC1925, 2.3 ]

             reply	other threads:[~2021-12-19 10:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-19 10:54 Thomas Bogendoerfer [this message]
2021-12-19 20:34 ` [GIT PULL] MIPS fixes for v5.16 pr-tracker-bot
  -- strict thread matches above, loose matches on Subject: below --
2021-11-27  9:43 Thomas Bogendoerfer
2021-11-27 18:58 ` pr-tracker-bot
2021-11-17 22:11 Thomas Bogendoerfer
2021-11-17 23:58 ` 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=20211219105455.GA3372@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.