linux-acpi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Tony Luck <tony.luck@gmail.com>
Cc: "Luck, Tony" <tony.luck@intel.com>,
	Borislav Petkov <bp@alien8.de>,
	"m.chehab@samsung.com" <m.chehab@samsung.com>,
	linux-acpi <linux-acpi@vger.kernel.org>
Subject: Re: [PATCH 5/7 REVISION v2] trace, RAS: Add eMCA trace event interface
Date: Fri, 20 Jun 2014 20:56:20 -0400	[thread overview]
Message-ID: <20140620205620.19a4a886@gandalf.local.home> (raw)
In-Reply-To: <CA+8MBbJCJjC1HJ3LnuzqSCZU+_=hNmRFD7sy7OgmGmFUJv=_ww@mail.gmail.com>

On Fri, 20 Jun 2014 16:01:52 -0700
Tony Luck <tony.luck@gmail.com> wrote:

> On Thu, Jun 19, 2014 at 7:06 PM, Chen, Gong <gong.chen@linux.intel.com> wrote:
> >> Add trace interface to elaborate all H/W error related information.
> >>
> > So, Steven & Tony
> >
> > How to solve the dependency between different git tree? (One for trace, One
> > for RAS)
> 
> 1) Simplest (for me) - Steve pushes the trace change upstream now (at
> -rc1 now, -rc2 on Sunday - dodgy, but possible).
> 
> 2) Steve puts the change in a topic branch and publishes to
> kernel.org. I clone that, and add eMCA patches on top
> 
> 3) Steve signs off the patch, and I put it into a RAS branch (awkward
> for Steve in subsequent changes to trace touch same areas)
> 
> 4) Something else
> 

I was going to go with #2 but I have some patches that need to go soon
and since this patch only adds a new macro that no one uses, maybe I
can still slip it in.

-- Steve

  reply	other threads:[~2014-06-21  0:56 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-11  8:34 New eMCA trace event interface V4 Chen, Gong
2014-06-11  8:34 ` [PATCH 1/7 v5] trace, RAS: Add basic RAS trace event Chen, Gong
2014-06-11 18:59   ` Borislav Petkov
2014-06-11  8:34 ` [PATCH 2/7 v3] trace, AER: Move trace into unified interface Chen, Gong
2014-06-11 19:00   ` Borislav Petkov
2014-06-11  8:34 ` [PATCH 3/7 v5] CPER: Adjust code flow of some functions Chen, Gong
2014-06-11  8:34 ` [PATCH 4/7 v2] RAS, debugfs: Add debugfs interface for RAS subsystem Chen, Gong
2014-06-11 19:01   ` Borislav Petkov
2014-06-11  8:34 ` [PATCH 5/7 v7] trace, RAS: Add eMCA trace event interface Chen, Gong
2014-06-11 19:02   ` Borislav Petkov
2014-06-12  2:42     ` Chen, Gong
2014-06-11  8:34 ` [PATCH 6/7 v4] trace, eMCA: Add a knob to adjust where to save event log Chen, Gong
2014-06-11  8:34 ` [PATCH 7/7] RAS, extlog: Adjust init flow Chen, Gong
2014-06-11 21:33 ` New eMCA trace event interface V4 Luck, Tony
2014-06-12  6:11 ` [PATCH 5/7 REVISION] trace, RAS: Add eMCA trace event interface Chen, Gong
2014-06-12 13:28   ` Steven Rostedt
2014-06-13  2:19     ` Chen, Gong
2014-06-13  3:01       ` Steven Rostedt
2014-06-13  3:08         ` Steven Rostedt
2014-06-13  7:09           ` Chen, Gong
2014-06-17  2:09             ` Chen, Gong
2014-06-17  3:37               ` Steven Rostedt
2014-06-17 12:59               ` Steven Rostedt
2014-06-18  2:33               ` eMCA trace interface update Chen, Gong
2014-06-18  2:33                 ` [PATCH 5/7 REVISION v2] trace, RAS: Add eMCA trace event interface Chen, Gong
2014-06-20  2:06                   ` Chen, Gong
2014-06-20 23:01                     ` Tony Luck
2014-06-21  0:56                       ` Steven Rostedt [this message]
2014-06-22 16:48                   ` Borislav Petkov
2014-06-23 23:51                     ` Luck, Tony
2014-06-24 10:20                       ` Borislav Petkov
2014-06-24 17:38                         ` Luck, Tony

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=20140620205620.19a4a886@gandalf.local.home \
    --to=rostedt@goodmis.org \
    --cc=bp@alien8.de \
    --cc=linux-acpi@vger.kernel.org \
    --cc=m.chehab@samsung.com \
    --cc=tony.luck@gmail.com \
    --cc=tony.luck@intel.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;
as well as URLs for NNTP newsgroup(s).