From: Richard Purdie <rpurdie@rpsys.net>
To: Florin Malita <fmalita@gmail.com>,
rmk+lkml@arm.linux.org.uk, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] PXA2xx: build PCMCIA as a module
Date: Thu, 05 Jan 2006 15:52:03 +0000 [thread overview]
Message-ID: <1136476323.6451.85.camel@localhost.localdomain> (raw)
In-Reply-To: <1136470671.14442.26.camel@scox.glenatl.glenayre.com>
On Thu, 2006-01-05 at 09:17 -0500, Florin Malita wrote:
> > On Wed, 2006-01-04 at 22:20 +0000, Richard Purdie wrote:
> > > NAK. This breaks poodle, tosa and collie who also use scoop and this
> > > pcmcia driver. I'd suggest moving scoop_pcmcia_config to
> > > arch/arm/common/scoop.c instead.
>
> Here's a version with the modified comment following your suggestion.
>
> Thanks,
> Florin
>
> Signed-off-by: Florin Malita <fmalita@gmail.com>
Signed-off-by: Richard Purdie <rpurdie@rpsys.net>
> --
> diff --git a/arch/arm/common/scoop.c b/arch/arm/common/scoop.c
> --- a/arch/arm/common/scoop.c
> +++ b/arch/arm/common/scoop.c
> @@ -19,6 +19,16 @@
>
> #define SCOOP_REG(d,adr) (*(volatile unsigned short*)(d +(adr)))
>
> +/* PCMCIA to Scoop linkage
> +
> + There is no easy way to link multiple scoop devices into one
> + single entity for the pxa2xx_pcmcia device so this structure
> + is used which is setup by the platform code and used by the
> + pcmcia driver.
> +*/
> +struct scoop_pcmcia_config *platform_scoop_config;
> +EXPORT_SYMBOL(platform_scoop_config);
> +
> struct scoop_dev {
> void *base;
> spinlock_t scoop_lock;
> diff --git a/drivers/pcmcia/pxa2xx_sharpsl.c b/drivers/pcmcia/pxa2xx_sharpsl.c
> --- a/drivers/pcmcia/pxa2xx_sharpsl.c
> +++ b/drivers/pcmcia/pxa2xx_sharpsl.c
> @@ -27,13 +27,6 @@
>
> #define NO_KEEP_VS 0x0001
>
> -/* PCMCIA to Scoop linkage
> -
> - There is no easy way to link multiple scoop devices into one
> - single entity for the pxa2xx_pcmcia device so this structure
> - is used which is setup by the platform code
> -*/
> -struct scoop_pcmcia_config *platform_scoop_config;
> #define SCOOP_DEV platform_scoop_config->devs
>
> static void sharpsl_pcmcia_init_reset(struct scoop_pcmcia_dev *scoopdev)
> diff --git a/drivers/pcmcia/soc_common.c b/drivers/pcmcia/soc_common.c
> --- a/drivers/pcmcia/soc_common.c
> +++ b/drivers/pcmcia/soc_common.c
> @@ -846,3 +846,4 @@ int soc_common_drv_pcmcia_remove(struct
>
> return 0;
> }
> +EXPORT_SYMBOL(soc_common_drv_pcmcia_remove);
>
>
prev parent reply other threads:[~2006-01-05 15:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-04 21:16 Florin Malita
2006-01-04 22:20 ` Richard Purdie
2006-01-05 0:12 ` Florin Malita
2006-01-05 14:17 ` Florin Malita
2006-01-05 15:52 ` Richard Purdie [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=1136476323.6451.85.camel@localhost.localdomain \
--to=rpurdie@rpsys.net \
--cc=fmalita@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk+lkml@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
Powered by JetHome