From: Kalle Valo <kalle.valo@iki.fi>
To: Christian Lamparter <chunkeey@web.de>
Cc: Johannes Berg <johannes@sipsolutions.net>,
"linux-wireless" <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] p54spi: remove arch specific dependencies
Date: Sat, 17 Jan 2009 10:10:15 +0200 [thread overview]
Message-ID: <87r6322w0o.fsf@litku.valot.fi> (raw)
In-Reply-To: <200901162234.15946.chunkeey@web.de> (Christian Lamparter's message of "Fri\, 16 Jan 2009 22\:34\:15 +0100")
Christian Lamparter <chunkeey@web.de> writes:
> On Friday 16 January 2009 20:33:43 Kalle Valo wrote:
>> N800 and N810 support is not on mainline yet, for stlc45xx I decided
>> to add module parameters for the gpio numbers. Here's the commit from
>> stlc45xx repo:
>>
>> http://gitorious.org/projects/stlc45xx/repos/mainline/commits/35afc5df0027d02d49e6f5bf986dcc4deb4ee6cf
>
> This is the same patch for p54spi.
> It removes all N800/N810 specific code from p54spi, so the driver can be used on
> other architectures, or configurations as well.
>
> Signed-off-by: Christian Lamparter <chunkeey@web.de>
> ---
> All in favour with these changes?
No complaints from me.
> +/*
> + * gpios should be handled in board files and provided via platform data,
> + * but because it's currently impossible for p54spi to have a header file
> + * in include/linux, let's use module paramaters for now
> + */
For stlc45xx, being an out-of-tree driver, it was impossible to have a
header file for the platform data. But p54spi is a proper in-tree
driver and it shouldn't have that problem. But that's the next step,
it shouldn't hold off this patch.
--
Kalle Valo
prev parent reply other threads:[~2009-01-17 8:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1LNgyq-0006iZ-0M@sipsolutions.net>
2009-01-16 9:30 ` p54 build failure Johannes Berg
2009-01-16 18:29 ` [PATCH] p54spi: fix build dependencies Christian Lamparter
2009-01-16 19:33 ` Kalle Valo
2009-01-16 21:34 ` [PATCH] p54spi: remove arch specific dependencies Christian Lamparter
2009-01-17 8:10 ` Kalle Valo [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=87r6322w0o.fsf@litku.valot.fi \
--to=kalle.valo@iki.fi \
--cc=chunkeey@web.de \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@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).