From: Haavard Skinnemoen <haavard.skinnemoen@atmel.com>
To: Pierre Ossman <drzeus-list@drzeus.cx>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/4] mmc: Export internal host state through debugfs
Date: Sat, 5 Jul 2008 15:44:36 +0200 [thread overview]
Message-ID: <20080705154436.27830440@siona.local> (raw)
In-Reply-To: <20080704194556.73061a08@mjolnir.drzeus.cx>
On Fri, 4 Jul 2008 19:45:56 +0200
Pierre Ossman <drzeus-list@drzeus.cx> wrote:
> I see that this version has no ifdef:s at all. Doesn't that mean a lot
> of useless code if DEBUG_FS is not enabled? You embedded guys are
> usually rather sensitive about such things. :)
Hmm...looks like gcc does a pretty poor job of eliminating unreachable
code, so we end up with about 1k of dead code in debugfs.o.
I guess we'll have to throw in a couple of #ifdefs then...
Haavard
next prev parent reply other threads:[~2008-07-05 13:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-30 16:35 [PATCH v5] Atmel MCI: Driver for Atmel on-chip MMC controllers Haavard Skinnemoen
2008-07-01 13:14 ` [PATCH v2 1/4] debugfs: Implement debugfs_remove_recursive() Haavard Skinnemoen
2008-07-01 13:14 ` [PATCH v2 2/4] mmc: Export internal host state through debugfs Haavard Skinnemoen
2008-07-01 13:14 ` [PATCH v2 3/4] mmc: Add per-card debugfs support Haavard Skinnemoen
2008-07-01 13:14 ` [PATCH v2 4/4] atmel-mci: " Haavard Skinnemoen
2008-07-04 17:45 ` [PATCH v2 2/4] mmc: Export internal host state through debugfs Pierre Ossman
2008-07-05 13:44 ` Haavard Skinnemoen [this message]
2008-07-10 8:33 ` Pierre Ossman
2008-07-10 11:17 ` Haavard Skinnemoen
2008-07-01 18:37 ` [PATCH v2 1/4] debugfs: Implement debugfs_remove_recursive() Greg KH
2008-07-01 19:12 ` Haavard Skinnemoen
2008-07-02 12:48 ` [PATCH v5] Atmel MCI: Driver for Atmel on-chip MMC controllers Haavard Skinnemoen
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=20080705154436.27830440@siona.local \
--to=haavard.skinnemoen@atmel.com \
--cc=drzeus-list@drzeus.cx \
--cc=linux-kernel@vger.kernel.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