linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: [PATCH] udev - advanced user query options
Date: Tue, 13 Jan 2004 19:47:32 +0000	[thread overview]
Message-ID: <20040113194732.GB3818@kroah.com> (raw)
In-Reply-To: <20040111023300.GA4762@vrfy.org>

On Tue, Jan 13, 2004 at 05:35:56AM +0100, Kay Sievers wrote:
> On Mon, Jan 12, 2004 at 05:04:45PM -0800, Greg KH wrote:
> > Very nice, applied.  But I did have to make one small change to get the
> > code to build properly with klibc:
> > 
> > > +static void print_record(char *path, struct udevice *dev)
> > > +{
> > > +	printf("P: %s\n", path);
> > > +	printf("N: %s\n", dev->name);
> > > +	printf("S: %s\n", dev->symlink);
> > > +	printf("O: %s\n", dev->owner);
> > > +	printf("G: %s\n", dev->group);
> > > +	printf("\n");
> > > +}
> > 
> > Turns out that gcc likes to convert single character printf() calls to
> > putchar() which is only defined in klibc as a macro :(
> 
> Just for information. This seems to fix the gcc with klibc :)

Thanks, I've reverted my change and applied this patch.

greg k-h


-------------------------------------------------------
This SF.net email is sponsored by: Perforce Software.
Perforce is the Fast Software Configuration Management System offering
advanced branching capabilities and atomic changes on 50+ platforms.
Free Eval! http://www.perforce.com/perforce/loadprog.html
_______________________________________________
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

  parent reply	other threads:[~2004-01-13 19:47 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-11  2:33 [PATCH] udev - advanced user query options Kay Sievers
2004-01-11  2:37 ` Robert Love
2004-01-11  3:17 ` Kay Sievers
2004-01-12 18:05 ` David Zeuthen
2004-01-12 21:21 ` Greg KH
2004-01-12 21:22 ` Greg KH
2004-01-12 23:56 ` Kay Sievers
2004-01-13  1:04 ` Greg KH
2004-01-13  1:21 ` Kay Sievers
2004-01-13  4:35 ` Kay Sievers
2004-01-13 18:29 ` Greg KH
2004-01-13 19:47 ` Greg KH [this message]
2004-01-15 13:54 ` Olaf Hering
2004-01-15 20:56 ` Greg KH
2004-01-15 21:16 ` Kay Sievers
2004-01-15 21:21 ` Greg KH
2004-01-16  9:49 ` Olaf Hering
2004-01-16  9:57 ` Kay Sievers
2004-01-16 21:54 ` Greg KH
2004-01-19  9:11 ` Olaf Hering
2004-01-19 17:47 ` Greg KH
2004-01-19 19:23 ` Olaf Hering
2004-01-20  0:08 ` 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=20040113194732.GB3818@kroah.com \
    --to=greg@kroah.com \
    --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 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).