From: Duncan Sands <baldrick@free.fr>
To: Oliver Neukum <oliver@neukum.org>, Greg KH <greg@kroah.com>
Cc: linux-usb-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org, Frederic Detienne <fd@cisco.com>
Subject: Re: [linux-usb-devel] [PATCH 7/9] USB usbfs: destroy submitted urbs only on the disconnected interface
Date: Thu, 15 Apr 2004 10:05:22 +0200 [thread overview]
Message-ID: <200404151005.22143.baldrick@free.fr> (raw)
In-Reply-To: <200404142239.08408.oliver@neukum.org>
On Wednesday 14 April 2004 22:39, Oliver Neukum wrote:
> > > I would prefer a real WARN_ON() so that the imbedded people compiling
> > > for size are not affected.
> >
> > What do you mean? How is a real WARN_ON() better?
>
> WARN_ON can be defined away to make a smaller kernel. Code that does
> not use it takes away that option.
Hi Oliver, I thought you meant that CONFIG_EMBEDDED made WARN_ON go away
(or something like that). If you just mean that it is easy to redefine WARN_ON by
hand, then all I can say is: it is also easy to redefine warn by hand! Anyway, I made
you the following patch:
--- gregkh-2.6/include/linux/usb.h.orig 2004-04-15 09:52:36.000000000 +0200
+++ gregkh-2.6/include/linux/usb.h 2004-04-15 09:56:30.000000000 +0200
@@ -1073,9 +1073,15 @@
#define dbg(format, arg...) do {} while (0)
#endif
-#define err(format, arg...) printk(KERN_ERR "%s: " format "\n" , __FILE__ , ## arg)
+#if !defined(CONFIG_EMBEDDED) || defined(DEBUG)
#define info(format, arg...) printk(KERN_INFO "%s: " format "\n" , __FILE__ , ## arg)
#define warn(format, arg...) printk(KERN_WARNING "%s: " format "\n" , __FILE__ , ## arg)
+#else
+#define info(format, arg...) do {} while (0)
+#define warn(format, arg...) do {} while (0)
+#endif
+
+#define err(format, arg...) printk(KERN_ERR "%s: " format "\n" , __FILE__ , ## arg)
#endif /* __KERNEL__ */
next prev parent reply other threads:[~2004-04-15 8:05 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-14 10:45 [PATCH 7/9] USB usbfs: destroy submitted urbs only on the disconnected interface Duncan Sands
2004-04-14 13:30 ` [linux-usb-devel] " Oliver Neukum
2004-04-14 13:38 ` Duncan Sands
2004-04-14 15:00 ` Duncan Sands
2004-04-14 15:33 ` Oliver Neukum
2004-04-14 15:39 ` Duncan Sands
2004-04-14 20:39 ` Oliver Neukum
2004-04-15 8:05 ` Duncan Sands [this message]
2004-04-15 8:31 ` Oliver Neukum
2004-04-15 8:47 ` Duncan Sands
2004-04-15 9:08 ` Oliver Neukum
2004-04-15 9:21 ` Duncan Sands
2004-04-14 16:48 ` Alan Stern
2004-04-14 17:09 ` Duncan Sands
2004-04-14 17:55 ` Alan Stern
2004-04-17 18:31 ` Duncan Sands
2004-04-17 18:53 ` Duncan Sands
2004-04-17 19:52 ` Alan Stern
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=200404151005.22143.baldrick@free.fr \
--to=baldrick@free.fr \
--cc=fd@cisco.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=oliver@neukum.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