mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Kathiravan Thirumoorthy <kathirav@codeaurora.org>
To: Suzuki K Poulose <suzuki.poulose@arm.com>, mathieu.poirier@linaro.org
Cc: mike.leach@linaro.org, alexander.shishkin@linux.intel.com,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] coresight: platform: use dev_warn instead of dev_warn_once
Date: Wed, 13 May 2020 18:06:36 +0530	[thread overview]
Message-ID: <2fda05b0-ed3d-7e48-6fab-2309d8a1ad56@codeaurora.org> (raw)
In-Reply-To: <2d59194a-2785-8762-81cd-bef34c6a51ec@arm.com>

On 5/11/2020 11:01 PM, Suzuki K Poulose wrote:
> On 05/11/2020 05:58 PM, Mathieu Poirier wrote:
>> Hi Kathiravan,
>>
>> On Fri, May 08, 2020 at 03:58:41PM +0530, Kathiravan T wrote:
>>> When more than one coresight components uses the obsolete DT bindings,
>>> warning is displayed for only one component and not for the others.
>>> Lets warn it for all components by replacing dev_warn_once with 
>>> dev_warn.
>>>
>>> Signed-off-by: Kathiravan T <kathirav@codeaurora.org>
>>> ---
>>>   drivers/hwtracing/coresight/coresight-platform.c | 2 +-
>>>   1 file changed, 1 insertion(+), 1 deletion(-)
>>>
>>> diff --git a/drivers/hwtracing/coresight/coresight-platform.c 
>>> b/drivers/hwtracing/coresight/coresight-platform.c
>>> index 43418a2..b7d9a02 100644
>>> --- a/drivers/hwtracing/coresight/coresight-platform.c
>>> +++ b/drivers/hwtracing/coresight/coresight-platform.c
>>> @@ -284,7 +284,7 @@ static int of_get_coresight_platform_data(struct 
>>> device *dev,
>>>       if (!parent) {
>>>           legacy_binding = true;
>>>           parent = node;
>>> -        dev_warn_once(dev, "Uses obsolete Coresight DT bindings\n");
>>> +        dev_warn(dev, "Uses obsolete Coresight DT bindings\n");
>>
>> We made a concious decision to use dev_warn_once() rather than 
>> dev_warn().
>> There can be a lot of coresight devices on a platform and warning for 
>> every
>> device doesn't do anything more than adding noise.
>>
>> If one device is using obsolete bindings the others very likely to do 
>> so as
>> well.  While fixing one device, checking the remaining devices should be
>> intuitive.
>
> Exactly ! Or someone could repeat the process until all are fixed ;-)
>
> Cheers
> Suzuki

Thanks Mathieu and Suzuki for the inputs. I shall drop this patch.

Thanks,

Kathiravan T.

      reply	other threads:[~2020-05-13 12:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-08 10:28 Kathiravan T
2020-05-11 16:58 ` Mathieu Poirier
2020-05-11 17:31   ` Suzuki K Poulose
2020-05-13 12:36     ` Kathiravan Thirumoorthy [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=2fda05b0-ed3d-7e48-6fab-2309d8a1ad56@codeaurora.org \
    --to=kathirav@codeaurora.org \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mathieu.poirier@linaro.org \
    --cc=mike.leach@linaro.org \
    --cc=suzuki.poulose@arm.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®