| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <20150521090152.182a46ef@gandalf.local.home> Date: Thu, 21 May 2015 09:01:52 -0400 From: Steven Rostedt <rostedt@...dmis.org> To: Borislav Petkov <bp@...e.de> Cc: Xie XiuQi <xiexiuqi@...wei.com>, akpm@...ux-foundation.org, n-horiguchi@...jp.nec.com, gong.chen@...ux.intel.com, mingo@...hat.com, tony.luck@...el.com, linux-kernel@...r.kernel.org, linux-mm@...ck.org, jingle.chen@...wei.com, sfr@...b.auug.org.au, rdunlap@...radead.org, jim.epost@...il.com Subject: Re: [PATCH v6 5/5] trace, ras: move ras_event.h under include/trace/events On Thu, 21 May 2015 11:24:37 +0200 Borislav Petkov <bp@...e.de> wrote: > On Thu, May 21, 2015 at 11:41:25AM +0800, Xie XiuQi wrote: > > From: Naoya Horiguchi <n-horiguchi@...jp.nec.com> > > > > Most of header files for tracepoints are located to include/trace/events or > > their relevant subdirectories under drivers/. One exception is > > That's simply not true. > > > include/ras/ras_events.h, which looks inconsistent. So let's move it to the > > default places for such headers. > > No thanks - ras TPs can live just fine in include/ras/. > I agree with Boris, the solution is not to move it. It's not inconsistent, lots of places use it. Just do a git grep -l TRACE_EVENT to see. -- Steve -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists