From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
Cc: linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org,
Sergio Paracuellos <sergio.paracuellos@gmail.com>
Subject: Re: [PATCH v2 0/4] MIPS: Cleanups to PCI related code
Date: Tue, 20 Feb 2024 14:39:14 +0100 [thread overview]
Message-ID: <ZdSrgqwuyEHUmgeq@alpha.franken.de> (raw)
In-Reply-To: <20240208120959.2513-1-ilpo.jarvinen@linux.intel.com>
On Thu, Feb 08, 2024 at 02:09:55PM +0200, Ilpo Järvinen wrote:
> Cleans up PCI related code.
>
> v2:
> - Convert also return 0 -> return PCIBIOS_SUCCESSFUL
>
> Ilpo Järvinen (4):
> MIPS: lantiq: Remove unused function pointer variables
> MIPS: ath79: Don't return PCIBIOS_* code from pcibios_enable_device()
> MIPS: PCI: Return PCIBIOS_* from tx4927_pci_config_read/write()
> MIPS: TXx9: Use PCI_SET_ERROR_RESPONSE()
>
> arch/mips/pci/fixup-ath79.c | 2 +-
> arch/mips/pci/fixup-lantiq.c | 9 ---------
> arch/mips/pci/ops-tx4927.c | 18 +++++++++++-------
> 3 files changed, 12 insertions(+), 17 deletions(-)
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:[~2024-02-20 13:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-08 12:09 Ilpo Järvinen
2024-02-08 12:09 ` [PATCH v2 1/4] MIPS: lantiq: Remove unused function pointer variables Ilpo Järvinen
2024-02-08 12:09 ` [PATCH v2 2/4] MIPS: ath79: Don't return PCIBIOS_* code from pcibios_enable_device() Ilpo Järvinen
2024-02-08 12:09 ` [PATCH v2 3/4] MIPS: PCI: Return PCIBIOS_* from tx4927_pci_config_read/write() Ilpo Järvinen
2024-02-08 12:09 ` [PATCH v2 4/4] MIPS: TXx9: Use PCI_SET_ERROR_RESPONSE() Ilpo Järvinen
2024-02-08 12:21 ` [PATCH v2 0/4] MIPS: Cleanups to PCI related code Sergio Paracuellos
2024-02-20 13:39 ` 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=ZdSrgqwuyEHUmgeq@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=sergio.paracuellos@gmail.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
all inboxes | Powered by JetHome®