From: Tobias Klauser <tklauser@access.unizh.ch>
To: linux-hotplug@vger.kernel.org
Subject: [PATCH] Fix GCC4 compile warnings
Date: Sun, 16 Jan 2005 18:09:00 +0000 [thread overview]
Message-ID: <41EAADBC.3050200@access.unizh.ch> (raw)
[-- Attachment #1: Type: text/plain, Size: 207 bytes --]
Hi
I tried to compile udev 050plus with the GCC 4.0 snapshot 200412119 and
got two errors about possibly uninitialized structs, so I fixed this.
The patch against udev050plus is attached.
Thanks, Tobias
[-- Attachment #2: udev050plus-gcc4-uninitialized-warning.patch --]
[-- Type: text/plain, Size: 615 bytes --]
--- udev-050plus.orig/udev_sysfs.c 2004-12-19 17:42:11.000000000 +0100
+++ udev-050plus/udev_sysfs.c 2005-01-16 19:00:32.978126432 +0100
@@ -381,7 +381,7 @@
struct sysfs_class_device *wait_class_device_open(const char *path)
{
- struct sysfs_class_device *class_dev;
+ struct sysfs_class_device *class_dev = NULL;
int loop;
loop = WAIT_MAX_SECONDS * WAIT_LOOP_PER_SECOND;
@@ -450,7 +450,7 @@
struct sysfs_device *wait_devices_device_open(const char *path)
{
- struct sysfs_device *devices_dev;
+ struct sysfs_device *devices_dev = NULL;
int loop;
loop = WAIT_MAX_SECONDS * WAIT_LOOP_PER_SECOND;
next reply other threads:[~2005-01-16 18:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-16 18:09 Tobias Klauser [this message]
2005-01-16 18:31 ` [PATCH] Fix GCC4 compile warnings Kay Sievers
2005-01-16 18:57 ` Kay Sievers
2005-01-16 19:09 ` Tobias Klauser
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=41EAADBC.3050200@access.unizh.ch \
--to=tklauser@access.unizh.ch \
--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).