public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: Tomasz Nowicki <tomasz.nowicki@linaro.org>, rjw@rjwysocki.net
Cc: lenb@kernel.org, tony.luck@intel.com, m.chehab@samsung.com,
	bp@suse.de, linux-edac@vger.kernel.org, x86@kernel.org,
	linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
	linaro-acpi@lists.linaro.org, rric@kernel.org
Subject: Re: [PATCH v4 2/3] acpi, apei, ghes: Make NMI error notification to be GHES architecture extension.
Date: Fri, 4 Jul 2014 12:37:31 +0200	[thread overview]
Message-ID: <20140704103731.GA9246@pd.tnic> (raw)
In-Reply-To: <53B64F3C.6080502@linaro.org>

On Fri, Jul 04, 2014 at 08:52:44AM +0200, Tomasz Nowicki wrote:
> Right, I will fix that and thanks for all you acks.
> 
> BTW, who else should I asked for review to move upstream process one step
> further?

I think you have enough people on CC and if they would find cycles to
review them, they're welcome to do so.

But the patches have gotten pretty neat and clean in the meantime so I
think Rafael could go over them quickly and maybe even pick them up...

:-)

-- 
Regards/Gruss,
    Boris.

Sent from a fat crate under my desk. Formatting is fine.
--

  reply	other threads:[~2014-07-04 10:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-24 11:41 [PATCH v4 0/3] APEI: Make APEI architecture independent Tomasz Nowicki
2014-06-24 11:41 ` [PATCH v4 1/3] apei, mce: Factor out APEI architecture specific MCE calls Tomasz Nowicki
2014-07-02 12:16   ` Borislav Petkov
2014-06-24 11:41 ` [PATCH v4 2/3] acpi, apei, ghes: Make NMI error notification to be GHES architecture extension Tomasz Nowicki
2014-07-02 12:16   ` Borislav Petkov
2014-07-04  6:52     ` Tomasz Nowicki
2014-07-04 10:37       ` Borislav Petkov [this message]
2014-06-24 11:41 ` [PATCH v4 3/3] acpi, apei, ghes: Factor out ioremap virtual memory for IRQ and NMI context Tomasz Nowicki
2014-07-02 12:17   ` Borislav Petkov

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=20140704103731.GA9246@pd.tnic \
    --to=bp@alien8.de \
    --cc=bp@suse.de \
    --cc=lenb@kernel.org \
    --cc=linaro-acpi@lists.linaro.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-edac@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=m.chehab@samsung.com \
    --cc=rjw@rjwysocki.net \
    --cc=rric@kernel.org \
    --cc=tomasz.nowicki@linaro.org \
    --cc=tony.luck@intel.com \
    --cc=x86@kernel.org \
    /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