From: Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Borislav Petkov <bp@suse.de>, Xie XiuQi <xiexiuqi@huawei.com>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"gong.chen@linux.intel.com" <gong.chen@linux.intel.com>,
"mingo@redhat.com" <mingo@redhat.com>,
"tony.luck@intel.com" <tony.luck@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"jingle.chen@huawei.com" <jingle.chen@huawei.com>,
"sfr@canb.auug.org.au" <sfr@canb.auug.org.au>,
"rdunlap@infradead.org" <rdunlap@infradead.org>,
"jim.epost@gmail.com" <jim.epost@gmail.com>
Subject: Re: [PATCH v6 5/5] trace, ras: move ras_event.h under include/trace/events
Date: Thu, 21 May 2015 23:00:24 +0000 [thread overview]
Message-ID: <20150521230024.GA4052@hori1.linux.bs1.fc.nec.co.jp> (raw)
In-Reply-To: <20150521090152.182a46ef@gandalf.local.home>
On Thu, May 21, 2015 at 09:01:52AM -0400, Steven Rostedt wrote:
> On Thu, 21 May 2015 11:24:37 +0200
> Borislav Petkov <bp@suse.de> wrote:
>
> > On Thu, May 21, 2015 at 11:41:25AM +0800, Xie XiuQi wrote:
> > > From: Naoya Horiguchi <n-horiguchi@ah.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.
My bad, I withdraw this patch.
Thanks,
Naoya Horiguchi
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2015-05-21 23:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-21 3:41 [PATCH v6 0/5] tracing: add trace event for memory-failure Xie XiuQi
2015-05-21 3:41 ` [PATCH v6 1/5] memory-failure: export page_type and action result Xie XiuQi
2015-05-21 3:41 ` [PATCH v6 2/5] memory-failure: change type of action_result's param 3 to enum Xie XiuQi
2015-05-21 3:41 ` [PATCH v6 3/5] tracing: add trace event for memory-failure Xie XiuQi
2015-05-21 3:41 ` [PATCH v6 4/5] tracing: fix build error in mm/memory-failure.c Xie XiuQi
2015-05-21 3:41 ` [PATCH v6 5/5] trace, ras: move ras_event.h under include/trace/events Xie XiuQi
2015-05-21 9:24 ` Borislav Petkov
2015-05-21 13:01 ` Steven Rostedt
2015-05-21 23:00 ` Naoya Horiguchi [this message]
2015-05-21 23:28 ` [PATCH v6 0/5] tracing: add trace event for memory-failure Naoya Horiguchi
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=20150521230024.GA4052@hori1.linux.bs1.fc.nec.co.jp \
--to=n-horiguchi@ah.jp.nec.com \
--cc=akpm@linux-foundation.org \
--cc=bp@suse.de \
--cc=gong.chen@linux.intel.com \
--cc=jim.epost@gmail.com \
--cc=jingle.chen@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@redhat.com \
--cc=rdunlap@infradead.org \
--cc=rostedt@goodmis.org \
--cc=sfr@canb.auug.org.au \
--cc=tony.luck@intel.com \
--cc=xiexiuqi@huawei.com \
/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