linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: hkallweit1@gmail.com (Heiner Kallweit)
To: linux-arm-kernel@lists.infradead.org
Subject: Small issue with 3fde2999fac5 "arm64: cpufeature: Don't dump useless backtrace on CPU_OUT_OF_SPEC"
Date: Mon, 5 Jun 2017 11:20:53 +0200	[thread overview]
Message-ID: <8ff72bb8-d8be-e691-c939-5f7d73f5e3d9@gmail.com> (raw)
In-Reply-To: <20170605084840.GB4650@leverpostej>

Am 05.06.2017 um 10:48 schrieb Mark Rutland:
> Hi,
> 
> On Sun, Jun 04, 2017 at 02:53:36PM +0200, Heiner Kallweit wrote:
>> The warning is printed unconditionally. An "if (taint)" seems to be
>> missing.
> 
> I'm not sure I follow. We're using pr_warn_once(), which should only
> print the message once, regardless of how many times it is called.
> 
Before we had WARN_TAINT_ONCE(taint, ..), so the warning is
triggered by taint != 0.
Now the warning is printed (just once but) even if taint == 0.

> Is that not working correctly for you?
> 
> If so, could you please report so on LAKML? That way others can get
> involved with investigating and fixing the issue.
> 
> Thanks,
> Mark.
> 

Rgds, Heiner

       reply	other threads:[~2017-06-05  9:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <7f8ade0a-c4ab-3e2e-d21e-8eab4df07cac@gmail.com>
     [not found] ` <20170605084840.GB4650@leverpostej>
2017-06-05  9:20   ` Heiner Kallweit [this message]
2017-06-05  9:24     ` Small issue with 3fde2999fac5 "arm64: cpufeature: Don't dump useless backtrace on CPU_OUT_OF_SPEC" Mark Rutland
2017-06-05  9:37       ` Heiner Kallweit
2017-06-05 10:46         ` 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=8ff72bb8-d8be-e691-c939-5f7d73f5e3d9@gmail.com \
    --to=hkallweit1@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).