From: Olaf Hering <olh@suse.de>
To: linux-hotplug@vger.kernel.org
Subject: Re: [ANNOUNCE] udev 013 release
Date: Mon, 19 Jan 2004 20:44:15 +0000 [thread overview]
Message-ID: <20040119204415.GB31967@suse.de> (raw)
In-Reply-To: <20040113235213.GA7659@kroah.com>
On Mon, Jan 19, Greg KH wrote:
> On Mon, Jan 19, 2004 at 09:29:00PM +0100, Olaf Hering wrote:
> > On Thu, Jan 15, Kay Sievers wrote:
> >
> > > +++ b/logging.h Thu Jan 15 15:22:25 2004
> >
> > > +#ifdef LOG
> > > +#include <syslog.h>
> >
> > > +#ifdef DEBUG
> > > +#define dbg(format, arg...) \
> > > + do { \
> > > + log_message (LOG_DEBUG , "%s: " format , __FUNCTION__ , ## arg); \
> >
> > This breaks with:
> >
> > make udevdir=/dev USE_LOGúlse USE_KLIBC=true DEBUG=true STRIP=/bin/true -j
> >
> > syslog.h does not depend on -DLOG
>
> Ick. This patch should fix this problem.
>
> If you make USE_LOGúlse, no debug messages will be sent out.
Is this correct? LOG_DEBUG is defined in syslog.h, this patch is
probably better.
--- udev.bk/logging.h~ 2004-01-15 22:00:58.000000000 +0000
+++ udev.bk/logging.h 2004-01-19 20:31:46.000000000 +0000
@@ -24,8 +24,9 @@
#ifndef LOGGING_H
#define LOGGING_H
-#ifdef LOG
#include <syslog.h>
+
+#ifdef LOG
#define info(format, arg...) \
do { \
log_message (LOG_INFO , format , ## arg); \
--
USB is for mice, FireWire is for men!
sUse lINUX ag, nÃœRNBERG
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2004-01-19 20:44 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-13 23:52 [ANNOUNCE] udev 013 release Greg KH
2004-01-13 23:52 ` Greg KH
2004-01-14 1:38 ` Frédéric L. W. Meunier
2004-01-14 2:14 ` Jon Smirl
2004-01-14 5:15 ` Nuno Silva
2004-01-14 17:15 ` Greg KH
2004-01-14 17:15 ` Greg KH
2004-01-14 17:46 ` Chris Friesen
2004-01-14 17:46 ` Chris Friesen
2004-01-14 19:23 ` Nuno Silva
2004-01-14 19:23 ` Nuno Silva
2004-01-14 21:14 ` Greg KH
2004-01-14 21:14 ` Greg KH
2004-01-15 7:48 ` Nuno Silva
2004-01-15 23:03 ` Greg KH
2004-01-15 23:03 ` Greg KH
2004-01-14 20:34 ` Clay Haapala
2004-01-14 20:34 ` Clay Haapala
2004-01-14 20:47 ` Chris Friesen
2004-01-14 20:47 ` Chris Friesen
2004-01-14 21:12 ` Greg KH
2004-01-14 21:12 ` Greg KH
2004-01-14 21:10 ` Greg KH
2004-01-14 21:10 ` Greg KH
2004-01-14 17:27 ` Greg KH
2004-01-15 4:14 ` Kay Sievers
2004-01-15 14:32 ` Kay Sievers
2004-01-15 22:40 ` Greg KH
2004-01-16 2:25 ` Nuno Silva
2004-01-16 3:24 ` Kay Sievers
2004-01-16 3:45 ` Nuno Silva
2004-01-19 20:29 ` Olaf Hering
2004-01-19 20:40 ` Greg KH
2004-01-19 20:44 ` Olaf Hering [this message]
2004-01-19 20:50 ` Greg KH
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=20040119204415.GB31967@suse.de \
--to=olh@suse.de \
--cc=linux-hotplug@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.