From: Borislav Petkov <bp@alien8.de>
To: Mauro Carvalho Chehab <mchehab@infradead.org>
Cc: Markus Trippelsdorf <markus@trippelsdorf.de>,
Ming Lei <tom.leiming@gmail.com>, Linda Walsh <lkml@tlinx.org>,
Linux-Kernel <linux-kernel@vger.kernel.org>,
Doug Thompson <dougthompson@xmission.com>,
linux-edac@vger.kernel.org
Subject: Re: BUG: key ffff880c1148c478 not in .data! (V3.10.0)
Date: Fri, 12 Jul 2013 16:21:06 +0200 [thread overview]
Message-ID: <20130712142106.GJ24008@pd.tnic> (raw)
In-Reply-To: <51E00B55.5070003@infradead.org>
On Fri, Jul 12, 2013 at 10:57:41AM -0300, Mauro Carvalho Chehab wrote:
> This will be overriding the content of the static var mc_bus every for
> every new memory controller. Are you sure that bus.name is only used
> on register, or if its contents is stored somewhere?
bus_register does kobject_set_name which copies bus->name, for example,
but I didn't look exhaustively.
Just to be on the safe side, I should probably do a
static const char **bus_names = { "mc0", "mc1", ..., "mc7" };
and use it. Are 8 enough for your edac drivers too?
--
Regards/Gruss,
Boris.
Sent from a fat crate under my desk. Formatting is fine.
--
next prev parent reply other threads:[~2013-07-12 14:21 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-07 22:25 Fwd: BUG: key ffff880c1148c478 not in .data! (V3.10.0) Linda Walsh
2013-07-12 2:19 ` Ming Lei
2013-07-12 8:04 ` Markus Trippelsdorf
2013-07-12 13:41 ` Borislav Petkov
2013-07-12 13:57 ` Mauro Carvalho Chehab
2013-07-12 14:21 ` Borislav Petkov [this message]
2013-07-12 16:13 ` Mauro Carvalho Chehab
2013-07-12 16:19 ` Luck, Tony
2013-07-18 16:42 ` Borislav Petkov
2013-07-18 16:51 ` Luck, Tony
2013-07-18 23:27 ` Borislav Petkov
2013-07-19 10:28 ` [PATCH -v2] EDAC: Fix lockdep splat Borislav Petkov
2013-07-20 3:55 ` Mauro Carvalho Chehab
2013-07-20 2:55 ` BUG: key ffff880c1148c478 not in .data! (V3.10.0) Mauro Carvalho Chehab
2013-07-12 14:28 ` Markus Trippelsdorf
2013-07-12 14:36 ` 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=20130712142106.GJ24008@pd.tnic \
--to=bp@alien8.de \
--cc=dougthompson@xmission.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@tlinx.org \
--cc=markus@trippelsdorf.de \
--cc=mchehab@infradead.org \
--cc=tom.leiming@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.