mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: "Colbert, Rusty" <rusty.colbert@hp.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Ingo Molnar <mingo@elte.hu>,
	"bluesmoke-devel@lists.sourceforge.net" 
	<bluesmoke-devel@lists.sourceforge.net>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/3] edac: Create an unique instance for each kobj
Date: Wed, 14 Oct 2009 12:21:38 -0300	[thread overview]
Message-ID: <20091014122138.2d12ca47@pedra.chehab.org> (raw)
In-Reply-To: <EC2969A33F12344780D895AFCAA422CE50861619C0@GVW1095EXB.americas.hpqcorp.net>

Em Wed, 14 Oct 2009 14:50:10 +0000
"Colbert, Rusty" <rusty.colbert@hp.com> escreveu:

> Is this all into a dev tree, or are there patches for a SLES 11 (2.6.27) ?

The patches at i7core_edac git tree aren't upstream. They are only at
development trees.
> 
> -----Original Message-----
> From: Mauro Carvalho Chehab [mailto:mchehab@redhat.com]
> Sent: Wednesday, October 14, 2009 4:42 AM
> To: Andrew Morton
> Cc: Ingo Molnar; bluesmoke-devel@lists.sourceforge.net; linux-kernel@vger.kernel.org
> Subject: Re: [PATCH 1/3] edac: Create an unique instance for each kobj
> 
> Hi Andrew,
> 
> Em Tue, 13 Oct 2009 20:01:17 -0700
> Andrew Morton <akpm@linux-foundation.org> escreveu:
> 
> > On Sun, 4 Oct 2009 16:43:54 -0300 Mauro Carvalho Chehab <mchehab@redhat.com> wrote:
> >
> > > Current code only works when there's just one memory
> > > controller, since we need one kobj for each instance.
> >
> > I don't know which kernel you're patching here, but it doesn't look
> > anything like mine...
> 
> It is on i7core_edac git tree. This tree were added to linux-next. You'll be
> able to see it starting from today's linux-next.
> 
> Cheers,
> Mauro
> 
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay
> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
> http://p.sf.net/sfu/devconference
> _______________________________________________
> bluesmoke-devel mailing list
> bluesmoke-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluesmoke-devel


-- 

Cheers,
Mauro

      reply	other threads:[~2009-10-14 15:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-24 22:28 [PATCH 00/63] i7core_edac and edac_mce Mauro Carvalho Chehab
2009-09-25  2:48 ` Hidetoshi Seto
2009-10-04 19:16 ` [PATCH 0/3] " Mauro Carvalho Chehab
2009-10-04 19:43 ` [PATCH 3/3] i7core_edac: Better parse "any" addrmask Mauro Carvalho Chehab
2009-10-04 19:43 ` [PATCH 2/3] i7core_edac: Use a lockless ringbuffer Mauro Carvalho Chehab
2009-10-04 19:43 ` [PATCH 1/3] edac: Create an unique instance for each kobj Mauro Carvalho Chehab
2009-10-14  3:01   ` Andrew Morton
2009-10-14  9:41     ` Mauro Carvalho Chehab
2009-10-14 14:50       ` Colbert, Rusty
2009-10-14 15:21         ` Mauro Carvalho Chehab [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=20091014122138.2d12ca47@pedra.chehab.org \
    --to=mchehab@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=bluesmoke-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rusty.colbert@hp.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

all inboxes | Powered by JetHome®