From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Jeff Garzik <jeff@garzik.org>
Cc: linux-fbdev-devel@lists.sourceforge.net, adaplas@gmail.com,
Andi Kleen <ak@suse.de>, LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [git patches] two warning fixes
Date: Thu, 19 Jul 2007 11:19:05 +1000 [thread overview]
Message-ID: <1184807945.25235.289.camel@localhost.localdomain> (raw)
In-Reply-To: <469EAABD.4010504@garzik.org>
On Wed, 2007-07-18 at 20:05 -0400, Jeff Garzik wrote:
> Andi Kleen wrote:
> > On Thursday 19 July 2007 01:55:04 Jeff Garzik wrote:
> >> Please pull from 'warnings' branch of
> >> master.kernel.org:/pub/scm/linux/kernel/git/jgarzik/misc-2.6.git warnings
> >>
> >> to receive the following updates:
> >>
> >> drivers/video/aty/radeon_base.c | 23 ++++++++++++++++++-----
> >> include/asm-x86_64/tlbflush.h | 6 +++++-
> >> 2 files changed, 23 insertions(+), 6 deletions(-)
> >>
> >> Jeff Garzik (2):
> >> drivers/video/aty/radeon_base: fix radeonfb_pci_register() err handling
> >> [X86-64] make flush_tlb_kernel_range() a static inline function
> >
> > I already got that patch queued. Why don't you send them through the maintainers?
>
> Because in both cases the maintainers never responded to me, indicating
> they were queued?
I suppose I should have acked the radeonfb one... I'm a bit of a slacker
with radeonfb maintainership lately.
However, in this case, I think I'll NACK it. I don't think it's fair to
fail the fb initialization because it couldn't create the EDID files. A
warning in dmesg is enough. For lots of machines, failing the fb init
means no console at all...
In general, I share paulus point of view here that forcing us to test
all those result code from sysfs file creation functions is just a major
PITA and adds bloat all over the kernel. There are many many cases where
the "obvious" thing of erroring out is actually not good policy. In many
cases, the failure to create some random sysfs file shouldn't prevent
the driver from operating, because the consequences of doing the later
are worse than the consequences of not having that sysfs file in the
first place. Thus, warnings are a better thing to do. But multiply the
number of sysfs_* calls by the code size of adding a test & printk and
you'll get the direct non-configurable-out bloat to the kernel.
Ben.
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
next prev parent reply other threads:[~2007-07-19 1:19 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-18 23:55 [git patches] two warning fixes Jeff Garzik
2007-07-18 23:59 ` Andi Kleen
2007-07-19 0:05 ` Jeff Garzik
2007-07-19 1:19 ` Benjamin Herrenschmidt [this message]
2007-07-19 1:41 ` Andrew Morton
2007-07-19 1:50 ` Linus Torvalds
2007-07-19 2:05 ` Benjamin Herrenschmidt
2007-07-19 2:36 ` Andrew Morton
2007-07-19 1:37 ` Linus Torvalds
2007-07-19 2:32 ` Jeff Garzik
2007-07-19 13:40 ` Krzysztof Halasa
2007-07-19 18:04 ` Linus Torvalds
2007-07-19 18:20 ` Stephen Hemminger
2007-07-20 18:34 ` Krzysztof Halasa
2007-07-21 0:32 ` Benjamin Herrenschmidt
2007-07-22 4:03 ` Jeff Garzik
2007-07-22 21:29 ` Benjamin Herrenschmidt
2007-07-23 3:26 ` Kyle Moffett
2007-07-19 13:38 ` Krzysztof Halasa
2007-07-19 18:00 ` Linus Torvalds
2007-07-20 12:54 ` Tim Tassonis
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=1184807945.25235.289.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=adaplas@gmail.com \
--cc=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=jeff@garzik.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).