From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: [PATCH 3/4] Fix -Wall warnings in udev 054 (chassis_id)
Date: Thu, 10 Mar 2005 17:52:59 +0000 [thread overview]
Message-ID: <1110477180.5137.88.camel@localhost.localdomain> (raw)
In-Reply-To: <20050310144021.GA4405@localhost.localdomain>
On Thu, 2005-03-10 at 15:40 +0100, Tobias Klauser wrote:
> Hi,
>
> The following patch fixes a warning when compiling chassis_id
> from udev with the -Wall compiler flag. There are too much
> conversions in the format string of sscanf(). One %d can be
> dropped.
>
> Thanks, Tobias
>
> Signed-off-by: Tobias Klauser <tklauser@access.unizh.ch>
>
> diff -urpN udev-054.orig/extras/chassis_id/table.c udev-054/extras/chassis_id/table.c
> --- udev-054.orig/extras/chassis_id/table.c 2005-03-01 21:19:49.000000000 +0100
> +++ udev-054/extras/chassis_id/table.c 2005-03-06 15:41:49.000000000 +0100
> @@ -59,7 +59,7 @@ int table_init(void)
> i = 0;
> while (!feof(fp)) {
> fgets(ptr, 80, fp);
> - sscanf(ptr, "%d %d %d %d %d %s %s", &ptable[i].id,
> + sscanf(ptr, "%d %d %d %d %s %s", &ptable[i].id,
> &ptable[i].num_disks,
> &ptable[i].chassis_num, &ptable[i].slot_num,
> ptable[i].serial_num, ptable[i].name);
Applied.
Thanks,
Kay
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_ide95&alloc_id\x14396&op=click
_______________________________________________
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
prev parent reply other threads:[~2005-03-10 17:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-10 14:40 [PATCH 3/4] Fix -Wall warnings in udev 054 (chassis_id) Tobias Klauser
2005-03-10 17:52 ` Kay Sievers [this message]
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=1110477180.5137.88.camel@localhost.localdomain \
--to=kay.sievers@vrfy.org \
--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).