From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Shang XiaoJing <shangxiaojing@huawei.com>
Cc: <agross@kernel.org>, <andersson@kernel.org>,
<konrad.dybcio@somainline.org>, <jejb@linux.ibm.com>,
<martin.petersen@oracle.com>, <linux-arm-msm@vger.kernel.org>,
<linux-scsi@vger.kernel.org>
Subject: Re: [PATCH -next] scsi: ufs: Remove redundant dev_err call
Date: Sat, 01 Oct 2022 05:29:39 -0400 [thread overview]
Message-ID: <yq18rlzlwna.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <20220923101217.18345-1-shangxiaojing@huawei.com> (Shang XiaoJing's message of "Fri, 23 Sep 2022 18:12:17 +0800")
Shang,
> devm_ioremap_resource() prints error message in itself. Remove the
> dev_err call to avoid redundant error message.
Applied to 6.1/scsi-staging, thanks!
--
Martin K. Petersen Oracle Linux Engineering
prev parent reply other threads:[~2022-10-01 9:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-23 10:12 [PATCH -next] scsi: ufs: Remove redundant dev_err call Shang XiaoJing
2022-09-30 18:06 ` Bart Van Assche
2022-10-01 9:29 ` Martin K. Petersen [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=yq18rlzlwna.fsf@ca-mkp.ca.oracle.com \
--to=martin.petersen@oracle.com \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=jejb@linux.ibm.com \
--cc=konrad.dybcio@somainline.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=shangxiaojing@huawei.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