From: Andy Kennedy <akennedy@techmoninc.com>
To: linux-mtd@lists.infradead.org
Subject: Re: backtrace.S & printk()
Date: Wed, 05 Sep 2007 11:23:42 -0500 [thread overview]
Message-ID: <46DED80E.5000802@techmoninc.com> (raw)
In-Reply-To: <20070905111743.0313e6b1@weaponx.rchland.ibm.com>
Josh Boyer wrote:
> On Wed, 05 Sep 2007 11:14:11 -0500
> Andy Kennedy <akennedy@techmoninc.com> wrote:
>
>
>> Russel:
>>
>> While attempting to build a kernel without printk in it, I ran across an
>> error in your backtrace.S file. It appears that you are assuming that
>> all arm kernels will be built with printk(). What is your reason for
>> this? What are the ramifications of me taking out those three sections
>> of code?
>>
>
> Erm... wrong list? This is the MTD list, not the ARM list...
>
> josh
>
> ______________________________________________________
> Linux MTD discussion mailing list
> http://lists.infradead.org/mailman/listinfo/linux-mtd/
>
>
>
Oh please. . . Linux-ARM Linux-MTD. . . it's all the same.
Bummer man. . . been a loooong week.
Andy
prev parent reply other threads:[~2007-09-05 16:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-05 16:14 backtrace.S & printk() Andy Kennedy
2007-09-05 16:17 ` Josh Boyer
2007-09-05 16:23 ` Andy Kennedy [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=46DED80E.5000802@techmoninc.com \
--to=akennedy@techmoninc.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox