From: "Chocron, Jonathan" <jonnyc@amazon.com>
To: "lorenzo.pieralisi@arm.com" <lorenzo.pieralisi@arm.com>,
"thomas.petazzoni@bootlin.com" <thomas.petazzoni@bootlin.com>,
"pratyush.anand@gmail.com" <pratyush.anand@gmail.com>,
"robh@kernel.org" <robh@kernel.org>,
"zhengdejin5@gmail.com" <zhengdejin5@gmail.com>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"bhelgaas@google.com" <bhelgaas@google.com>,
"tjoseph@cadence.com" <tjoseph@cadence.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v1] PCI: controller: Remove duplicate error message
Date: Tue, 26 May 2020 18:22:56 +0000 [thread overview]
Message-ID: <1d7703d5c29dc9371ace3645377d0ddd9c89be30.camel@amazon.com> (raw)
In-Reply-To: <20200526150954.4729-1-zhengdejin5@gmail.com>
On Tue, 2020-05-26 at 23:09 +0800, Dejin Zheng wrote:
> CAUTION: This email originated from outside of the organization. Do
> not click links or open attachments unless you can confirm the sender
> and know the content is safe.
>
>
>
> It will print an error message by itself when
> devm_pci_remap_cfg_resource() goes wrong. so remove the duplicate
> error message.
>
It seems like that in the first error case in
devm_pci_remap_cfg_resource(), the print will be less indicative. Could
you please share an example print log with the duplicate print?
Thanks,
Jonathan
next prev parent reply other threads:[~2020-05-26 19:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-26 15:09 Dejin Zheng
2020-05-26 18:22 ` Chocron, Jonathan [this message]
2020-05-27 13:20 ` Dejin Zheng
2020-06-02 7:44 ` Chocron, Jonathan
2020-06-02 15:01 ` Rob Herring
2020-07-06 15:58 ` Lorenzo Pieralisi
2020-07-11 7:47 ` Dejin Zheng
2020-07-15 16:45 ` Lorenzo Pieralisi
2020-07-17 13:44 ` Dejin Zheng
2020-06-01 22:13 ` Rob Herring
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=1d7703d5c29dc9371ace3645377d0ddd9c89be30.camel@amazon.com \
--to=jonnyc@amazon.com \
--cc=bhelgaas@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=pratyush.anand@gmail.com \
--cc=robh@kernel.org \
--cc=thomas.petazzoni@bootlin.com \
--cc=tjoseph@cadence.com \
--cc=zhengdejin5@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®