public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@amd64.org>
To: Mauro Carvalho Chehab <mchehab@redhat.com>
Cc: Randy Dunlap <rdunlap@xenotime.net>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	Doug Thompson <dougthompson@xmission.com>,
	Borislav Petkov <borislav.petkov@amd.com>,
	linux-edac@vger.kernel.org
Subject: Re: linux-next: Tree for Jun 5 (amd64_edac)
Date: Tue, 5 Jun 2012 19:27:15 +0200	[thread overview]
Message-ID: <20120605172715.GQ13495@aftab.osrc.amd.com> (raw)
In-Reply-To: <4FCE40C3.5040902@redhat.com>

On Tue, Jun 05, 2012 at 02:24:19PM -0300, Mauro Carvalho Chehab wrote:
> Em 05-06-2012 14:17, Borislav Petkov escreveu:
> > On Tue, Jun 05, 2012 at 09:26:39AM -0700, Randy Dunlap wrote:
> >> On 06/04/2012 08:30 PM, Stephen Rothwell wrote:
> >>
> >>> Hi all,
> >>>
> >>> There will be no linux-next release tomorrow.
> >>>
> >>> Changes since 20120604:
> >>
> >>
> >>
> >> on x86_64:
> >>
> >> drivers/edac/amd64_edac_inj.o: In function `amd64_remove_sysfs_dbg_files':
> >> amd64_edac_inj.c:(.text+0x420): multiple definition of `amd64_remove_sysfs_dbg_files'
> >> drivers/edac/amd64_edac.o:amd64_edac.c:(.text+0x3d60): first defined here
> >> make[3]: *** [drivers/edac/amd64_edac_mod.o] Error 1
> > 
> > Doesn't trigger on latest linus. But Mauro has a bunch of patches
> > touching these parts, can you try reverting if it is in linux-next, the
> > one below:
> > 
> > commit faf20d4e226c53a963c384d36d8aa82c77be6dfb
> > Author: Mauro Carvalho Chehab <mchehab@redhat.com>
> > Date:   Wed Mar 21 14:00:44 2012 -0300
> > 
> >     amd64_edac: convert sysfs logic to use struct device
> >     
> >     Now that the EDAC core supports struct device, there's no sense
> >     on having any logic at the EDAC core to simulate it. So, instead
> >     of adding such logic there, change the logic at amd64_edac to
> >     use it.
> >     
> >     Reviewed-by: Aristeu Rozanski <arozansk@redhat.com>
> >     Cc: Doug Thompson <norsk5@yahoo.com>
> >     Cc: Borislav Petkov <borislav.petkov@amd.com>
> >     Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
> > 
> > Thanks.
> > 
> 
> It is probably just a Kconfig issue. I'll prepare a patch fixing it,
> posting it soon.

Just add it to the above patch - it is not merged anywhere anyway.

-- 
Regards/Gruss,
Boris.

Advanced Micro Devices GmbH
Einsteinring 24, 85609 Dornach
GM: Alberto Bozzo
Reg: Dornach, Landkreis Muenchen
HRB Nr. 43632 WEEE Registernr: 129 19551

  reply	other threads:[~2012-06-05 17:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-05  3:30 linux-next: Tree for Jun 5 Stephen Rothwell
2012-06-05 16:26 ` linux-next: Tree for Jun 5 (amd64_edac) Randy Dunlap
2012-06-05 17:17   ` Borislav Petkov
2012-06-05 17:24     ` Mauro Carvalho Chehab
2012-06-05 17:27       ` Borislav Petkov [this message]
2012-06-05 17:38   ` Mauro Carvalho Chehab
2012-06-06 13:16     ` Borislav Petkov
2012-06-06 21:30     ` 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=20120605172715.GQ13495@aftab.osrc.amd.com \
    --to=bp@amd64.org \
    --cc=borislav.petkov@amd.com \
    --cc=dougthompson@xmission.com \
    --cc=linux-edac@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mchehab@redhat.com \
    --cc=rdunlap@xenotime.net \
    --cc=sfr@canb.auug.org.au \
    /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