From: Helge Deller <deller@gmx.de>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Kyle McMartin <kyle@mcmartin.ca>,
linux-parisc <linux-parisc@vger.kernel.org>
Subject: Re: [PATCH] parisc: BUG_ON() cleanup
Date: Tue, 06 Jan 2009 17:09:55 +0100 [thread overview]
Message-ID: <49638253.6000807@gmx.de> (raw)
In-Reply-To: <1231255233.7090.5.camel@localhost.localdomain>
James Bottomley wrote:
> On Tue, 2009-01-06 at 12:57 +0100, Helge Deller wrote:
>> - convert a few "if (xx) BUG();" to BUG_ON(xx)
>
> This is fine
>
>> - remove a few printk()s, as we get a backtrace with BUG_ON() anyway
>
> This is less helpful. Each of the printks explains why the bug
> triggers. In theory you can work this out from the BUG_ON line number,
> but *only* if your source files match those of the reporter, which isn't
> the case in an annoyingly large number of bug reports ... speaking as
> someone who seems to get to diagnose large numbers of bugs, it makes my
> life harder.
I fully understand your point.
Regarding arch/parisc/kernel/pci-dma.c:
- each of the pa11_dma_map_* functions where I removed the printks only had
one BUG() anyway. Should be easy to find it in backtraces.
- a few of the pa11_dma_map_* functions have printks, the others don't. I just
made it consistent.
Regarding arch/parisc/mm/init.c:
- setup_bootmem() is a huge function. I agree that keeping this printk would
make sense.
So, would you be OK with the patch if I drop the init.c change and keep the
pci-dma.c changes?
Helge
next prev parent reply other threads:[~2009-01-06 16:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-06 11:57 [PATCH] parisc: BUG_ON() cleanup Helge Deller
2009-01-06 15:20 ` James Bottomley
2009-01-06 16:09 ` Helge Deller [this message]
2009-01-06 16:49 ` Mike Frysinger
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=49638253.6000807@gmx.de \
--to=deller@gmx.de \
--cc=James.Bottomley@HansenPartnership.com \
--cc=kyle@mcmartin.ca \
--cc=linux-parisc@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 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.