Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.kernel > #1170244 > unrolled thread

[PATCH 0/2] x86/mm/pat: don't use WARN for nopat requirement

Back to article view | Back to linux.kernel

Contents

  [PATCH 0/2] x86/mm/pat: don't use WARN for nopat requirement "Luis R. Rodriguez" <mcgrof@do-not-panic.com> - 2015-06-23 00:40 +0200

#1170244 — [PATCH 0/2] x86/mm/pat: don't use WARN for nopat requirement

From: "Luis R. Rodriguez" <mcgrof@suse.com>

Mauro, Doug,

The 0-day robot found using WARN() on built-in kernels confusing. Upon
further thought pr_warn() is better and will likely also not confuse
humans too.

Boris, provided maintainers Ack, please consider these patches.

These depend on pat_enabled() exported symbol which went in through
the x86 tree, so I suppose this also needs to go through there. This
is an example issue of cross-tree collateral evolution follow ups,
one reason why I punted the a RFD and proposal for a linux-oven [0].
In that regard I suppose follow ups like these would need to go through
that tree as well.

[0] http://lkml.kernel.org/r/20150619231255.GC7487@garbanzo.do-not-panic.com

Luis R. Rodriguez (2):
  x86/mm/pat, drivers/infiniband/ipath: replace WARN() with pr_warn()
  x86/mm/pat, drivers/media/ivtv: replace WARN() with pr_warn()

 drivers/infiniband/hw/ipath/ipath_driver.c | 6 ++++--
 drivers/media/pci/ivtv/ivtvfb.c            | 6 ++++--
 2 files changed, 8 insertions(+), 4 deletions(-)

-- 
2.3.2.209.gd67f9d5.dirty

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [standalone]

Back to top | Article view | linux.kernel

csiph-web