All of lore.kernel.org
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@suse.de>
To: lkp@lists.01.org
Subject: Re: [x86/mm/pat, drivers/media/ivtv] WARNING: CPU: 0 PID: 1 at drivers/media/pci/ivtv/ivtvfb.c:1270 ivtvfb_init()
Date: Mon, 22 Jun 2015 09:06:41 +0200	[thread overview]
Message-ID: <20150622070641.GA19872@pd.tnic> (raw)
In-Reply-To: <20150622010138.GQ11147@wotan.suse.de>

[-- Attachment #1: Type: text/plain, Size: 587 bytes --]

On Mon, Jun 22, 2015 at 03:01:38AM +0200, Luis R. Rodriguez wrote:
> We can certainly replace the WARN() with pr_warn(), I don't see
> how its confusing though as its a run time real issue. Either
> way whatever you recommend is fine by me.

Yeah, it confused the 0day robot at least. :-)

But maybe because it cannot really read. But I've experienced cases
where people don't read too, see *a* splat and raise the alarm. So yeah,
I think a simple pr_warn would be much better.

Thanks.

-- 
Regards/Gruss,
    Boris.

ECO tip #101: Trim your mails when you reply.
--

WARNING: multiple messages have this Message-ID (diff)
From: Borislav Petkov <bp@suse.de>
To: "Luis R. Rodriguez" <mcgrof@suse.com>
Cc: Fengguang Wu <fengguang.wu@intel.com>,
	Ingo Molnar <mingo@kernel.org>,
	linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
	LKP <lkp@01.org>
Subject: Re: [x86/mm/pat, drivers/media/ivtv]  WARNING: CPU: 0 PID: 1 at drivers/media/pci/ivtv/ivtvfb.c:1270 ivtvfb_init()
Date: Mon, 22 Jun 2015 09:06:41 +0200	[thread overview]
Message-ID: <20150622070641.GA19872@pd.tnic> (raw)
In-Reply-To: <20150622010138.GQ11147@wotan.suse.de>

On Mon, Jun 22, 2015 at 03:01:38AM +0200, Luis R. Rodriguez wrote:
> We can certainly replace the WARN() with pr_warn(), I don't see
> how its confusing though as its a run time real issue. Either
> way whatever you recommend is fine by me.

Yeah, it confused the 0day robot at least. :-)

But maybe because it cannot really read. But I've experienced cases
where people don't read too, see *a* splat and raise the alarm. So yeah,
I think a simple pr_warn would be much better.

Thanks.

-- 
Regards/Gruss,
    Boris.

ECO tip #101: Trim your mails when you reply.
--
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in

WARNING: multiple messages have this Message-ID (diff)
From: Borislav Petkov <bp@suse.de>
To: "Luis R. Rodriguez" <mcgrof@suse.com>
Cc: Fengguang Wu <fengguang.wu@intel.com>,
	Ingo Molnar <mingo@kernel.org>,
	linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
	LKP <lkp@01.org>
Subject: Re: [x86/mm/pat, drivers/media/ivtv]  WARNING: CPU: 0 PID: 1 at drivers/media/pci/ivtv/ivtvfb.c:1270 ivtvfb_init()
Date: Mon, 22 Jun 2015 09:06:41 +0200	[thread overview]
Message-ID: <20150622070641.GA19872@pd.tnic> (raw)
In-Reply-To: <20150622010138.GQ11147@wotan.suse.de>

On Mon, Jun 22, 2015 at 03:01:38AM +0200, Luis R. Rodriguez wrote:
> We can certainly replace the WARN() with pr_warn(), I don't see
> how its confusing though as its a run time real issue. Either
> way whatever you recommend is fine by me.

Yeah, it confused the 0day robot at least. :-)

But maybe because it cannot really read. But I've experienced cases
where people don't read too, see *a* splat and raise the alarm. So yeah,
I think a simple pr_warn would be much better.

Thanks.

-- 
Regards/Gruss,
    Boris.

ECO tip #101: Trim your mails when you reply.
--
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
Please read the FAQ at  http://www.tux.org/lkml/

  reply	other threads:[~2015-06-22  7:06 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-20  7:17 [x86/mm/pat, drivers/media/ivtv] WARNING: CPU: 0 PID: 1 at drivers/media/pci/ivtv/ivtvfb.c:1270 ivtvfb_init() Fengguang Wu
2015-06-20  7:17 ` Fengguang Wu
2015-06-20 11:08 ` Borislav Petkov
2015-06-20 11:08   ` Borislav Petkov
2015-06-20 11:08   ` Borislav Petkov
2015-06-21 20:23   ` Luis R. Rodriguez
2015-06-21 20:23     ` Luis R. Rodriguez
2015-06-21 20:23     ` Luis R. Rodriguez
2015-06-21 20:41     ` Borislav Petkov
2015-06-21 20:41       ` Borislav Petkov
2015-06-21 20:41       ` Borislav Petkov
2015-06-22  1:01       ` Luis R. Rodriguez
2015-06-22  1:01         ` Luis R. Rodriguez
2015-06-22  1:01         ` Luis R. Rodriguez
2015-06-22  7:06         ` Borislav Petkov [this message]
2015-06-22  7:06           ` Borislav Petkov
2015-06-22  7:06           ` Borislav Petkov
2015-06-22 17:19           ` Luis R. Rodriguez
2015-06-22 17:19             ` Luis R. Rodriguez
2015-06-22 17:19             ` Luis R. Rodriguez
2015-06-22  6:36       ` Ingo Molnar
2015-06-22  6:36         ` Ingo Molnar
2015-06-22  6:36         ` Ingo Molnar

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=20150622070641.GA19872@pd.tnic \
    --to=bp@suse.de \
    --cc=lkp@lists.01.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.