[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <TYAP286MB0315167833A9801E56BBFE91BC5DA@TYAP286MB0315.JPNP286.PROD.OUTLOOK.COM>
Date: Wed, 21 Jun 2023 09:03:56 +0800
From: Shiji Yang <yangshiji66@...look.com>
To: sergio.paracuellos@...il.com
Cc: angelogioacchino.delregno@...labora.com,
linux-kernel@...r.kernel.org, linux-mediatek@...ts.infradead.org,
linux-mips@...r.kernel.org, matthias.bgg@...il.com,
tsbogend@...ha.franken.de
Subject: Re: [PATCH 0/2] mips: pci-mt7620: reduce unnecessary error logs
>On Tue, Jun 20, 2023 at 12:48 PM Shiji Yang <yangshiji66@...look.com> wrote:
>>
>> These patches silence some mt7620 PCIe driver error messeges by
>> removing the useless debugging codes and replacing incorrectly
>> used 'dev_err()' with 'dev_info()'.
>>
>> Shiji Yang (2):
>> mips: pci-mt7620: do not print NFTS register value as error log
>> mips: pci-mt7620: use dev_info() to log PCIe device detection result
>>
>> arch/mips/pci/pci-mt7620.c | 7 ++-----
>> 1 file changed, 2 insertions(+), 5 deletions(-)
>
>For the series:
>Reviewed-by: Sergio Paracuellos <sergio.paracuellos@...il.com>
>
>I'd really love to have this driver ported to PCI_DRIVERS_GENERIC
>moved to 'drivers/pci/controller/pcie-mt7621.c' since they are pretty
>similar just changing that mt7620 and mt7628 init the hardware
>different and only use one virtual bridge. My problem is that I don't
>have and cannot find hardware to test. Do you have interest in helping
>me to do this?
Thanks,
Sergio Paracuellos
Thank you for rewriting these drivers! I am glad to help test them. Please
let me know at any time when they are ready.
Best regards,
Shiji Yang
Powered by blists - more mailing lists