From: Robin Murphy <robin.murphy@arm.com>
To: Sai Prakash Ranjan <saiprakash.ranjan@codeaurora.org>,
Doug Anderson <dianders@chromium.org>,
Will Deacon <will@kernel.org>
Cc: Joerg Roedel <joro@8bytes.org>,
iommu@lists.linux-foundation.org,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-arm-msm <linux-arm-msm@vger.kernel.org>
Subject: Re: [PATCHv2] iommu/arm-smmu: Make remove callback message more informative
Date: Thu, 7 May 2020 11:33:38 +0100 [thread overview]
Message-ID: <2f3cd963-dffe-290b-02bf-819687713738@arm.com> (raw)
In-Reply-To: <0b5098c28360d018f390a97155b9776c@codeaurora.org>
On 2020-05-07 11:04 am, Sai Prakash Ranjan wrote:
> Hi,
>
> On 2020-05-07 05:40, Doug Anderson wrote:
>> Hi,
>>
>> On Thu, Apr 23, 2020 at 7:35 AM Doug Anderson <dianders@chromium.org>
>> wrote:
>>>
>>> Hi,
>>>
>>> On Thu, Apr 23, 2020 at 2:55 AM Sai Prakash Ranjan
>>> <saiprakash.ranjan@codeaurora.org> wrote:
>>> >
>>> > Currently on reboot/shutdown, the following messages are
>>> > displayed on the console as error messages before the
>>> > system reboots/shutdown as part of remove callback.
>>> >
>>> > On SC7180:
>>> >
>>> > arm-smmu 15000000.iommu: removing device with active domains!
>>> > arm-smmu 5040000.iommu: removing device with active domains!
>>> >
>>> > Make this error message more informative and less scary.
>>> >
>>> > Reported-by: Douglas Anderson <dianders@chromium.org>
>>> > Suggested-by: Robin Murphy <robin.murphy@arm.com>
>>> > Signed-off-by: Sai Prakash Ranjan <saiprakash.ranjan@codeaurora.org>
>>> > ---
>>> > drivers/iommu/arm-smmu.c | 2 +-
>>> > 1 file changed, 1 insertion(+), 1 deletion(-)
>>>
>>> Reviewed-by: Douglas Anderson <dianders@chromium.org>
>>
>> Is this patch waiting on anything in particular now? Do we need
>> reviews from Robin and/or Will?
>>
>
> Waiting for their reviews as they are the maintainers/reviewers :)
Sorry, this did register at the time, I just felt that it's a bit
redundant to give a review tag to say "yes, this is exactly what I
suggested" :)
That said, I do wish I hadn't forgotten about the dev_notice message
level, but I think that lies over in the conceptual purity corner rather
than making any practical difference, so I'm still OK with the patch
as-is. Will?
Robin.
p.s. whoever has this entry in their address book for the IOMMU list
(Doug?):
"list@263.net:IOMMU DRIVERS <iommu@lists.linux-foundation.org>, Joerg
Roedel <joro@8bytes.org>," <iommu@lists.linux-foundation.org>
it really messes up Thunderbird's ability to generate working headers
for a reply ;)
next prev parent reply other threads:[~2020-05-07 10:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-23 9:55 [PATCHv2] iommu/arm-smmu: Make remove callback message more informative Sai Prakash Ranjan
2020-04-23 14:35 ` Doug Anderson
2020-05-07 0:10 ` Doug Anderson
2020-05-07 10:04 ` Sai Prakash Ranjan
2020-05-07 10:33 ` Robin Murphy [this message]
2020-05-07 11:05 ` Sai Prakash Ranjan
2020-05-07 14:04 ` Will Deacon
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=2f3cd963-dffe-290b-02bf-819687713738@arm.com \
--to=robin.murphy@arm.com \
--cc=dianders@chromium.org \
--cc=iommu@lists.linux-foundation.org \
--cc=joro@8bytes.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=saiprakash.ranjan@codeaurora.org \
--cc=will@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox