From: Artem Bityutskiy <dedekind1@gmail.com>
To: "Fache, Herve" <h-fache@ti.com>
Cc: joern@lazybastard.org, joern@logfs.org, linux-mtd@lists.infradead.org
Subject: Re: [PATCH] phram: make kernel boot command line arguments work
Date: Tue, 25 Oct 2011 10:32:56 +0300 [thread overview]
Message-ID: <1319528005.14178.2.camel@golum> (raw)
In-Reply-To: <CA+Xn3W3huOu_zu7MzSr0W1wpo7mD_ek8eOYNstkMnb9wm3-JZw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 609 bytes --]
On Fri, 2011-10-21 at 10:49 +0200, Fache, Herve wrote:
> > Accessing __initdata from non __init function. Please check that your
> > patch does not introduce a new section mismatch. There is even a kernel
> > config option to debug these issues.
>
> I enabled DEBUG_SECTION_MISMATCH but I don't get errors. Also, this
> part of the code will never be reached once init has run. If you think
> that it's a risk, then I can remove the __initdata keyword.
Did you test this for the case when it is compiled into the kernel as
well, not only as kernel module?
--
Best Regards,
Artem Bityutskiy
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 490 bytes --]
next prev parent reply other threads:[~2011-10-25 7:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-17 15:40 [PATCH] phram: make kernel boot command line arguments work h-fache
2011-10-18 0:32 ` Jörn Engel
2011-10-18 8:05 ` Fache, Herve
2011-10-20 16:34 ` Artem Bityutskiy
2011-10-20 16:16 ` Artem Bityutskiy
2011-10-21 8:51 ` Fache, Herve
2011-10-25 7:37 ` Artem Bityutskiy
2011-10-25 9:09 ` Fache, Herve
2011-10-25 19:58 ` Jörn Engel
2011-10-29 20:10 ` Artem Bityutskiy
2011-10-20 16:20 ` Artem Bityutskiy
2011-10-21 8:49 ` Fache, Herve
2011-10-25 7:32 ` Artem Bityutskiy [this message]
2011-10-25 9:07 ` Fache, Herve
2011-10-29 20:09 ` Artem Bityutskiy
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=1319528005.14178.2.camel@golum \
--to=dedekind1@gmail.com \
--cc=h-fache@ti.com \
--cc=joern@lazybastard.org \
--cc=joern@logfs.org \
--cc=linux-mtd@lists.infradead.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 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.