From: Finn Thain <fthain@telegraphics.com.au>
To: Kars de Jong <jongk@linux-m68k.org>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
linux-m68k@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/4] m68k/mac: More printk modernization
Date: Sat, 28 Oct 2017 13:04:25 +1100 (AEDT) [thread overview]
Message-ID: <alpine.LNX.2.00.1710281242550.3@nippy.intranet> (raw)
In-Reply-To: <alpine.LNX.2.00.1710280923440.3@nippy.intranet>
On Sat, 28 Oct 2017, I wrote:
> > Any particular reason why you didn't use pr_debug() here? I'm guessing
> > it's because this is not a known pointer value?
> >
>
> It's because the call to psc_debug_dump() is already conditional on
> #ifdef DEBUG_PSC.
>
> Having the printk conditional on both DEBUG and DEBUG_PSC would be
> annoying. And I didn't want an unconditional call to psc_debug_dump()
> because I think PSC_DEBUG could become more useful given that PSC
> support is woefully incomplete.
>
Perhaps PSC_DEBUG should be scrapped in favour of DEBUG. Presently
DEBUG_PSC is set and I think that's useful as long as those drivers are
incomplete. So we would end up with this:
#define DEBUG
#include ...
...
static void psc_debug_dump(void)
{
...
pr_debug(...);
...
}
void __init psc_init(void)
{
...
#if DEBUG
psc_debug_dump()
#endif
...
}
In this version, the "#define DEBUG" at the top of the file has obscure
side effects (not just in printk.h) considering all of the headers that
get included, and their includes, and so on. I still prefer the patch that
I sent.
--
next prev parent reply other threads:[~2017-10-28 2:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-27 2:45 [PATCH 0/4] m68k/mac: Various cleanups and fixes Finn Thain
2017-10-27 2:45 ` [PATCH 3/4] m68k/mac: Disentangle VIA/RBV and NuBus initialization Finn Thain
2017-10-27 2:45 ` [PATCH 1/4] m68k/mac: More printk modernization Finn Thain
2017-10-27 10:59 ` Kars de Jong
2017-10-27 22:35 ` Finn Thain
2017-10-28 2:04 ` Finn Thain [this message]
2017-10-27 2:45 ` [PATCH 2/4] m68k/mac: Disentangle VIA and OSS initialization Finn Thain
2017-10-27 11:00 ` Kars de Jong
2017-10-27 11:02 ` Kars de Jong
[not found] ` <CACz-3rgGZcdd3RZZm8Q7PxVtWsMmYLaXk_qEnb8LN2oUHSz6pQ@mail.gmail.com>
2017-10-27 22:23 ` Finn Thain
2017-10-27 2:45 ` [PATCH 4/4] m68k/mac: Add mutual exclusion for IOP interrupt polling Finn Thain
2017-11-09 22:09 ` [PATCH 0/4] m68k/mac: Various cleanups and fixes Geert Uytterhoeven
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=alpine.LNX.2.00.1710281242550.3@nippy.intranet \
--to=fthain@telegraphics.com.au \
--cc=geert@linux-m68k.org \
--cc=jongk@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@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