All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: "Pali Rohár" <pali@kernel.org>
Cc: "Maciej W. Rozycki" <macro@orcam.me.uk>,
	linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/2] MIPS: Cobalt: Explain GT64111 early PCI fixup
Date: Wed, 3 Nov 2021 17:36:17 +0100	[thread overview]
Message-ID: <20211103163617.GA9984@alpha.franken.de> (raw)
In-Reply-To: <20211102171259.9590-2-pali@kernel.org>

On Tue, Nov 02, 2021 at 06:12:59PM +0100, Pali Rohár wrote:
> Properly document why changing PCI Class Code for GT64111 device to Host
> Bridge is required as important details were after 20 years forgotten.
> 
> Signed-off-by: Pali Rohár <pali@kernel.org>
> 
> ---
> Changes in v2:
> * Split from ARM changes
> * Removal of Kconfig changes
> * Explanation is completely rewritten as as this MIPS Cobalt device
>   predates ARM Orion devices and reason is slightly different.
> ---
>  arch/mips/pci/fixup-cobalt.c | 15 +++++++++++++++
>  1 file changed, 15 insertions(+)

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 ]

  reply	other threads:[~2021-11-03 16:43 UTC|newest]

Thread overview: 58+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-01 15:04 [PATCH] PCI: Marvell: Update PCIe fixup Pali Rohár
2021-11-01 15:04 ` Pali Rohár
2021-11-01 16:27 ` Jason Gunthorpe
2021-11-01 16:27   ` Jason Gunthorpe
2021-11-01 17:56   ` Pali Rohár
2021-11-01 17:56     ` Pali Rohár
2021-11-01 18:03     ` Jason Gunthorpe
2021-11-01 18:03       ` Jason Gunthorpe
2021-11-02  8:42 ` Thomas Bogendoerfer
2021-11-02  8:42   ` Thomas Bogendoerfer
2021-11-02  9:02   ` Pali Rohár
2021-11-02  9:02     ` Pali Rohár
2021-11-02  9:47     ` Thomas Bogendoerfer
2021-11-02  9:47       ` Thomas Bogendoerfer
2021-11-02 10:00       ` Pali Rohár
2021-11-02 10:00         ` Pali Rohár
2021-11-02 12:35         ` Maciej W. Rozycki
2021-11-02 12:35           ` Maciej W. Rozycki
2021-11-02 12:58           ` Pali Rohár
2021-11-02 12:58             ` Pali Rohár
2021-11-02 14:01             ` Maciej W. Rozycki
2021-11-02 14:01               ` Maciej W. Rozycki
2021-11-02 14:49               ` Pali Rohár
2021-11-02 14:49                 ` Pali Rohár
2021-11-02 15:48                 ` Pali Rohár
2021-11-02 15:48                   ` Pali Rohár
2021-11-02 17:03                   ` Stefan Roese
2021-11-02 17:03                     ` Stefan Roese
2021-11-03 14:59                   ` Maciej W. Rozycki
2021-11-03 14:59                     ` Maciej W. Rozycki
2021-11-03 14:49                 ` Maciej W. Rozycki
2021-11-03 14:49                   ` Maciej W. Rozycki
2021-11-03 15:03                   ` Pali Rohár
2021-11-03 15:03                     ` Pali Rohár
2021-11-02 15:02         ` Thomas Bogendoerfer
2021-11-02 15:02           ` Thomas Bogendoerfer
2021-11-02 15:13           ` Pali Rohár
2021-11-02 15:13             ` Pali Rohár
2021-11-09 23:42             ` Pali Rohár
2021-11-09 23:42               ` Pali Rohár
2021-11-10  8:55               ` Thomas Bogendoerfer
2021-11-10  8:55                 ` Thomas Bogendoerfer
2021-11-02 17:12 ` [PATCH v2 1/2] ARM: " Pali Rohár
2021-11-02 17:12   ` Pali Rohár
2021-11-02 17:12   ` [PATCH v2 2/2] MIPS: Cobalt: Explain GT64111 early PCI fixup Pali Rohár
2021-11-03 16:36     ` Thomas Bogendoerfer [this message]
2021-11-09 22:53   ` [PATCH v2 1/2] ARM: Marvell: Update PCIe fixup Pali Rohár
2021-11-09 22:53     ` Pali Rohár
2022-05-14 18:21     ` Pali Rohár
2022-05-14 18:21       ` Pali Rohár
2022-07-07 18:31       ` Pali Rohár
2022-07-07 18:31         ` Pali Rohár
2022-07-07 19:22         ` Russell King (Oracle)
2022-07-07 19:22           ` Russell King (Oracle)
2022-02-19 14:30   ` Pali Rohár
2022-02-19 14:30     ` Pali Rohár
2022-07-18 10:34     ` Gregory CLEMENT
2022-07-18 10:34       ` Gregory CLEMENT

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=20211103163617.GA9984@alpha.franken.de \
    --to=tsbogend@alpha.franken.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=macro@orcam.me.uk \
    --cc=pali@kernel.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.