public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Len Brown <lenb@kernel.org>
To: Huang Ying <ying.huang@intel.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"Luck, Tony" <tony.luck@intel.com>,
	"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
	Andi Kleen <andi@firstfloor.org>
Subject: Re: [PATCH 0/7] ACPI, APEI patches for 2.6.39
Date: Wed, 23 Mar 2011 00:16:25 -0400 (EDT)	[thread overview]
Message-ID: <alpine.LFD.2.02.1103230013260.10549@x980> (raw)
In-Reply-To: <1300762892.3616.12.camel@yhuang-mobile.sh.intel.com>

> > > > [PATCH 1/7] Add Kconfig option ARCH_HAVE_NMI_SAFE_CMPXCHG
> > > > [PATCH 2/7] lib, Add lock-less NULL terminated single list

> > > > [PATCH 3/7] ACPI, APEI, Add ERST record ID cache
> > > > [PATCH 4/7] PCIe, AER, use pre-generated prefix in error information printing
> > > > [PATCH 5/7] ACPI, APEI, Add PCIe AER error information printing support

I'll submit just 3,4,5/7 for upstream w/ the ACPI tree.
I'd like to see andrew take 1,2,6 (which now need to be refreshed)
in mm and when they ship, that will enable 7/7, which is the reason
that they exist.

thanks,
-Len

> > > > [PATCH 6/7] lib, Make gen_pool memory allocator lockless
> > > > [PATCH 7/7] ACPI, APEI, GHES, printk support for recoverable error via NMI
> > > 
> > > I've put this series into acpi-test, so it will be visible in linux-next;
> > > but I'm not the right person to review the generic lockless stuff,
> > > who is?
> > 
> > I reviewed it earlier and it seemed good to me (unless it has 
> > changed), but Linus wanted non Intel reviewers too. Any takers?
> 
> As for
> 
> [PATCH 1/7] Add Kconfig option ARCH_HAVE_NMI_SAFE_CMPXCHG
> [PATCH 2/7] lib, Add lock-less NULL terminated single list
> [PATCH 6/7] lib, Make gen_pool memory allocator lockless
> 
> they are general kernel patches.  I remember you have reviewed some
> earlier version of these patches, and merged 1/2 into -mm tree.  Do you
> have time to review these patches?  Although Andi has reviewed them, we
> really need some non-Intel reviewers.
> 
> Thanks,
> Huang Ying
> b
> 

      reply	other threads:[~2011-03-23  4:16 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-21  5:54 [PATCH 0/7] ACPI, APEI patches for 2.6.39 Huang Ying
2011-02-21  5:54 ` [PATCH 1/7] Add Kconfig option ARCH_HAVE_NMI_SAFE_CMPXCHG Huang Ying
2011-02-21  5:54 ` [PATCH 2/7] lib, Add lock-less NULL terminated single list Huang Ying
2011-02-21  5:54 ` [PATCH 3/7] ACPI, APEI, Add ERST record ID cache Huang Ying
2011-02-21  5:54 ` [PATCH 4/7] PCIe, AER, use pre-generated prefix in error information printing Huang Ying
2011-02-21  5:54 ` [PATCH 5/7] ACPI, APEI, Add PCIe AER error information printing support Huang Ying
2011-02-21  5:54 ` [PATCH 6/7] lib, Make gen_pool memory allocator lockless Huang Ying
2011-02-21  5:54 ` [PATCH 7/7] ACPI, APEI, GHES, printk support for recoverable error via NMI Huang Ying
2011-03-02 22:51 ` [PATCH 0/7] ACPI, APEI patches for 2.6.39 Len Brown
2011-03-03  0:01   ` Andi Kleen
2011-03-22  3:01     ` Huang Ying
2011-03-23  4:16       ` Len Brown [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=alpine.LFD.2.02.1103230013260.10549@x980 \
    --to=lenb@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=andi@firstfloor.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tony.luck@intel.com \
    --cc=ying.huang@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