public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: Chen Gong <gong.chen@linux.intel.com>,
	Wei Yongjun <weiyj.lk@gmail.com>,
	"lenb@kernel.org" <lenb@kernel.org>,
	"yongjun_wei@trendmicro.com.cn" <yongjun_wei@trendmicro.com.cn>,
	"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>
Subject: Re: [PATCH] ACPI / APEI: fix error return code in einj_init()
Date: Thu, 13 Jun 2013 00:51:34 +0200	[thread overview]
Message-ID: <1564755.IPcJhbuUt7@vostro.rjw.lan> (raw)
In-Reply-To: <3908561D78D1C84285E8C5FCA982C28F2DA7A526@ORSMSX106.amr.corp.intel.com>

On Wednesday, June 12, 2013 01:42:02 PM Luck, Tony wrote:
> > Well, as it happens, all of these patches are in my tree as well. :-)
> 
> Excellent!
> 
> > I actually didn't know that there was a separate path to Linus for APEI
> > material.
> 
> It's one of the many gray areas ... APEI is clearly part of ACPI, but it is also
> all about RAS too.

Yes, it is.

> > Do you want to handle it going forward or do you want me to do that?  Or do
> > you want me to pull it from you?
> 
> I think I'd like to take them into my tree and then have you pull them
> into the ACPI tree.

OK

Going forward I won't pick up any APEI patches from the list unless you tell
me to do that.

Thanks,
Rafael


-- 
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.

      reply	other threads:[~2013-06-12 22:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-05  2:17 [PATCH] ACPI / APEI: fix error return code in einj_init() Wei Yongjun
2013-06-05  2:59 ` Chen Gong
2013-06-11 22:26   ` Rafael J. Wysocki
2013-06-11 23:04     ` Luck, Tony
2013-06-12 11:13       ` Rafael J. Wysocki
2013-06-12 13:42         ` Luck, Tony
2013-06-12 22:51           ` Rafael J. Wysocki [this message]

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=1564755.IPcJhbuUt7@vostro.rjw.lan \
    --to=rjw@sisk.pl \
    --cc=gong.chen@linux.intel.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=tony.luck@intel.com \
    --cc=weiyj.lk@gmail.com \
    --cc=yongjun_wei@trendmicro.com.cn \
    /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