public inbox for kernel-janitors@vger.kernel.org
 help / color / mirror / Atom feed
* [tip:perf/core 86/90] arch/x86/kernel/cpu/perf_event.h:377:43: sparse: dubious one-bit signed bitfie
@ 2012-07-06 17:52 wfg
  2012-07-09 11:52 ` [tip:perf/core 86/90] arch/x86/kernel/cpu/perf_event.h:377:43: sparse: dubious one-bit signed bi Peter Zijlstra
  0 siblings, 1 reply; 2+ messages in thread
From: wfg @ 2012-07-06 17:52 UTC (permalink / raw)
  To: kernel-janitors

Hi Peter,

Should we make the bits "unsigned"?

tree:   git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git perf/core
head:   6a67943a18c264d5f3df436da38edb3e59adc905
commit: 3e0091e2b6f8cd59e567f247e345a3a6ad1f6e7e [86/90] perf/x86: Save a few bytes in 'struct x86_pmu'

All sparse warnings:

+ arch/x86/kernel/cpu/perf_event.h:377:43: sparse: dubious one-bit signed bitfield
  arch/x86/kernel/cpu/perf_event.h:378:43: sparse: dubious one-bit signed bitfield
  arch/x86/kernel/cpu/perf_event.h:379:43: sparse: dubious one-bit signed bitfield
  arch/x86/kernel/cpu/perf_event.h:380:43: sparse: dubious one-bit signed bitfield
  arch/x86/kernel/cpu/perf_event.h:381:43: sparse: dubious one-bit signed bitfield

vim +377 arch/x86/kernel/cpu/perf_event.h
   374		/*
   375		 * Intel DebugStore bits
   376		 */
 > 377		int		bts		:1,
   378				bts_active	:1,
   379				pebs		:1,
   380				pebs_active	:1,

---
0-DAY kernel build testing backend         Open Source Technology Centre
Fengguang Wu <wfg@linux.intel.com>                     Intel Corporation

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2012-07-09 11:52 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2012-07-06 17:52 [tip:perf/core 86/90] arch/x86/kernel/cpu/perf_event.h:377:43: sparse: dubious one-bit signed bitfie wfg
2012-07-09 11:52 ` [tip:perf/core 86/90] arch/x86/kernel/cpu/perf_event.h:377:43: sparse: dubious one-bit signed bi Peter Zijlstra

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox