From: "Randy.Dunlap" <rddunlap@osdl.org>
To: Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] pdc4030: return needs value; function needs return;
Date: Tue, 9 Sep 2003 21:34:39 -0700 [thread overview]
Message-ID: <20030909213439.4723e2b0.rddunlap@osdl.org> (raw)
In-Reply-To: <200309100314.26305.bzolnier@elka.pw.edu.pl>
On Wed, 10 Sep 2003 03:14:26 +0200 Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl> wrote:
|
| Hi,
|
| On Wednesday 10 of September 2003 01:54, Randy.Dunlap wrote:
| > @@ -317,7 +317,7 @@ int __init ide_probe_for_pdc4030(void)
| > #endif
| > }
| > }
| > -#ifdef MODULE
| > +#ifndef MODULE
| > return 0;
| > #endif
| > }
|
| This is wrong, we will now get warning for module instead of built-in.
| Proper fix is to remove this #ifdef.
Yes, sorry about that.
Here's the corrected patch for 2.6.0-test5.
--
~Randy
patch_name: pdc4030_returns.patch
patch_version: 2003-09-09.21:27:28
author: Randy.Dunlap <rddunlap@osdl.org>
description: return needs a value; function needs a return;
product: Linux
product_versions: 260-test5
maintainer: B.Zolnierkiewicz@elka.pw.edu.pl
diffstat: =
drivers/ide/legacy/pdc4030.c | 4 +---
1 files changed, 1 insertion(+), 3 deletions(-)
diff -Naur ./drivers/ide/legacy/pdc4030.c~pdcleg ./drivers/ide/legacy/pdc4030.c
--- ./drivers/ide/legacy/pdc4030.c~pdcleg 2003-09-08 12:50:06.000000000 -0700
+++ ./drivers/ide/legacy/pdc4030.c 2003-09-09 21:25:20.000000000 -0700
@@ -304,7 +304,7 @@
#ifndef MODULE
if (enable_promise_support == 0)
- return;
+ return 0;
#endif
for (index = 0; index < MAX_HWIFS; index++) {
@@ -317,9 +317,7 @@
#endif
}
}
-#ifdef MODULE
return 0;
-#endif
}
static void __exit release_pdc4030(ide_hwif_t *hwif, ide_hwif_t *mate)
prev parent reply other threads:[~2003-09-10 4:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-09 23:54 Randy.Dunlap
2003-09-10 1:14 ` Bartlomiej Zolnierkiewicz
2003-09-10 4:34 ` Randy.Dunlap [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=20030909213439.4723e2b0.rddunlap@osdl.org \
--to=rddunlap@osdl.org \
--cc=B.Zolnierkiewicz@elka.pw.edu.pl \
--cc=akpm@osdl.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®