From: Shiji Yang <yangshiji66@outlook.com>
To: sergio.paracuellos@gmail.com
Cc: angelogioacchino.delregno@collabora.com,
linux-kernel@vger.kernel.org, linux-mediatek@lists.infradead.org,
linux-mips@vger.kernel.org, matthias.bgg@gmail.com,
tsbogend@alpha.franken.de
Subject: Re: [PATCH 0/2] mips: pci-mt7620: reduce unnecessary error logs
Date: Wed, 21 Jun 2023 09:03:56 +0800 [thread overview]
Message-ID: <TYAP286MB0315167833A9801E56BBFE91BC5DA@TYAP286MB0315.JPNP286.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <CAMhs-H96z65X5L-8=ouuKS-fkBUS4Uo4GTaYYgMDkw5G+v73hQ@mail.gmail.com>
>On Tue, Jun 20, 2023 at 12:48 PM Shiji Yang <yangshiji66@outlook.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@gmail.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
next prev parent reply other threads:[~2023-06-21 1:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-20 10:43 Shiji Yang
2023-06-20 11:20 ` Sergio Paracuellos
2023-06-21 1:03 ` Shiji Yang [this message]
2023-06-21 6:40 ` Sergio Paracuellos
2023-06-21 14:07 ` Thomas Bogendoerfer
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=TYAP286MB0315167833A9801E56BBFE91BC5DA@TYAP286MB0315.JPNP286.PROD.OUTLOOK.COM \
--to=yangshiji66@outlook.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-mips@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=sergio.paracuellos@gmail.com \
--cc=tsbogend@alpha.franken.de \
/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®