public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Borislav Petkov <bp@alien8.de>,
	Randy Dunlap <rdunlap@xenotime.net>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-edac@vger.kernel.org
Subject: Re: Linux 3.1-rc1 (i7core_edac build error)
Date: Tue, 09 Aug 2011 07:01:03 -0300	[thread overview]
Message-ID: <4E41055F.9010900@redhat.com> (raw)
In-Reply-To: <20110808213159.GA22088@liondog.tnic>

Em 08-08-2011 18:31, Borislav Petkov escreveu:
> On Mon, Aug 08, 2011 at 01:59:31PM -0700, Randy Dunlap wrote:
>> on x86_64:
>>
>> ERROR: "x86_mce_decoder_chain" [drivers/edac/i7core_edac.ko] undefined!
>>
>> Full kernel (rand)config file is attached.
> 
> This has got to be linux-next because the x86_mce_decoder_chain for
> i7core_edac is not upstream yet, AFAICT.
> 
> If so, then
> 
> http://git.kernel.org/?p=linux/kernel/git/mchehab/edac.git;a=commitdiff;h=cd90cc84c6bf0f40a681900c609c044336a1b12e
> 
> needs to be changed to depend on X86_MCE. Mauro, you want an updated
> patch or you don't rebase your linux-next branch and need a diff ontop?

I don't think that anyone, except for -next, is cloning from my tree,
and there are just a few new patches there, so I'm not caring a lot of 
not doing rebase on this tree, but incremantal patches is better.

Thanks,
Mauro

  parent reply	other threads:[~2011-08-09 10:01 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-08  2:25 Linux 3.1-rc1 Linus Torvalds
2011-08-08 20:59 ` Linux 3.1-rc1 (i7core_edac build error) Randy Dunlap
2011-08-08 21:31   ` Borislav Petkov
2011-08-08 21:37     ` Randy Dunlap
2011-08-09 10:01     ` Mauro Carvalho Chehab [this message]
2011-08-10 12:43       ` [PATCH] EDAC: Correct Kconfig dependencies Borislav Petkov
2011-08-10 17:14         ` Randy Dunlap
2011-08-11 16:26           ` Borislav Petkov
2011-08-08 21:35 ` Linux 3.1-rc1 (staging/comedi) Randy Dunlap
2011-08-08 21:37   ` Randy Dunlap
2011-08-08 21:51   ` Greg KH
2011-08-08 23:32     ` Randy Dunlap
2011-08-10 18:22 ` [PATCH mainline] xen: xen-selfballoon.c needs more header files Randy Dunlap
2011-08-10 19:20   ` Konrad Rzeszutek Wilk
2011-08-10 19:23 ` Linux 3.1-rc1 (nfs/pnfs and drivers/md) Randy Dunlap
2011-08-11  0:35   ` Peng Tao
2011-08-11  0:58     ` Randy Dunlap
2011-08-11  1:10       ` Linus Torvalds
2011-08-11  3:26         ` tao.peng
2011-08-11  6:06           ` Christoph Hellwig
2011-08-11  6:21             ` tao.peng
2011-08-11 10:11           ` Benny Halevy
2011-08-11 18:44             ` Boaz Harrosh
2011-08-11 21:10               ` [PATCH] pnfs: Automatically select blocks & objects layouts Boaz Harrosh
2011-08-11 21:29                 ` [PATCH v2] " Boaz Harrosh
2011-08-11 21:43                   ` Randy Dunlap
2011-08-11 21:53                     ` Boaz Harrosh
2011-08-11 22:13                 ` [PATCH] " Jim Rees
2011-08-11 23:47                   ` Peng Tao
2011-08-11 15:41           ` Linux 3.1-rc1 (nfs/pnfs and drivers/md) Randy Dunlap

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=4E41055F.9010900@redhat.com \
    --to=mchehab@redhat.com \
    --cc=bp@alien8.de \
    --cc=linux-edac@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@xenotime.net \
    --cc=torvalds@linux-foundation.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