From: Andrew Morton <akpm@digeo.com>
To: Felipe Alfaro Solana <felipe_alfaro@linuxmail.org>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Russell King <rmk@arm.linux.org.uk>
Subject: Re: 2.5.68-mm3
Date: Wed, 30 Apr 2003 02:59:15 -0700 [thread overview]
Message-ID: <20030430025915.1692ffdd.akpm@digeo.com> (raw)
In-Reply-To: <1051696273.591.4.camel@teapot.felipe-alfaro.com>
Felipe Alfaro Solana <felipe_alfaro@linuxmail.org> wrote:
>
> drivers/pcmcia/cs.c: In function `pcmcia_register_socket':
> drivers/pcmcia/cs.c:361: `dev' undeclared (first use in this function)
> drivers/pcmcia/cs.c:361: (Each undeclared identifier is reported only
> once
> drivers/pcmcia/cs.c:361: for each function it appears in.)
> drivers/pcmcia/cs.c: At top level:
> drivers/pcmcia/cs.c:391: conflicting types for
> `pcmcia_unregister_socket'
diff -puN drivers/pcmcia/cs.c~pcmcia-fix drivers/pcmcia/cs.c
--- 25/drivers/pcmcia/cs.c~pcmcia-fix 2003-04-30 02:55:46.000000000 -0700
+++ 25-akpm/drivers/pcmcia/cs.c 2003-04-30 02:58:54.000000000 -0700
@@ -303,7 +303,7 @@ static int proc_read_clients(char *buf,
======================================================================*/
static int pccardd(void *__skt);
-void pcmcia_unregister_socket(struct device *dev);
+static void pcmcia_unregister_socket(struct class_device *class_dev);
#define to_class_data(dev) dev->class_data
@@ -358,7 +358,7 @@ int pcmcia_register_socket(struct class_
spin_lock_init(&s->thread_lock);
ret = kernel_thread(pccardd, s, CLONE_KERNEL);
if (ret < 0) {
- pcmcia_unregister_socket(dev);
+ pcmcia_unregister_socket(class_dev);
break;
}
@@ -387,7 +387,7 @@ int pcmcia_register_socket(struct class_
/**
* pcmcia_unregister_socket - remove a pcmcia socket device
*/
-void pcmcia_unregister_socket(struct class_device *class_dev)
+static void pcmcia_unregister_socket(struct class_device *class_dev)
{
struct pcmcia_socket_class_data *cls_d = class_get_devdata(class_dev);
unsigned int i;
_
_
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
next prev parent reply other threads:[~2003-04-30 9:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-30 6:59 2.5.68-mm3 Andrew Morton
2003-04-30 9:51 ` 2.5.68-mm3 Felipe Alfaro Solana
2003-04-30 9:59 ` Andrew Morton [this message]
2003-04-30 18:35 ` 2.5.68-mm3 Greg KH
2003-04-30 22:58 ` 2.5.68-mm3 Felipe Alfaro Solana
2003-04-30 23:57 ` 2.5.68-mm3 Ed Tomlinson
2003-05-01 0:04 ` 2.5.68-mm3 Andrew Morton
2003-05-01 3:18 ` 2.5.68-mm3 steven roemen
2003-05-01 17:47 ` 2.5.68-mm3 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=20030430025915.1692ffdd.akpm@digeo.com \
--to=akpm@digeo.com \
--cc=felipe_alfaro@linuxmail.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rmk@arm.linux.org.uk \
/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