From: Chris Ball <cjb@laptop.org>
To: Jeremie Samuel <jeremie.samuel.ext@parrot.com>
Cc: linux-mmc@vger.kernel.org,
"Grégor Boirie" <gregor.boirie@parrot.com>,
"Matthieu Castet" <matthieu.castet@parrot.com>,
"Anton Vorontsov" <avorontsov@mvista.com>
Subject: Re: [PATCH 3/8] sdhci: Use work structs instead of tasklets
Date: Mon, 21 Oct 2013 12:44:20 +0100 [thread overview]
Message-ID: <86li1mq25n.fsf@void.printf.net> (raw)
In-Reply-To: <5264E78B.1020209@parrot.com> (Jeremie Samuel's message of "Mon, 21 Oct 2013 10:36:27 +0200")
Hi Jeremie,
On Mon, Oct 21 2013, Jeremie Samuel wrote:
> Do you have a way for me to compile the driver for all the
> architectures impacted by the patch? So I could send a patch which
> compile for all these architectures.
If you can get an ARM cross-compiler going, it would look something
like this:
$ mkdir obj.dove obj.imx obj.s3c obj.spear obj.tegra
$ cp arch/arm/configs/dove_defconfig obj.dove
$ cp arch/arm/configs/imx_v6_v7_defconfig obj.imx
$ cp arch/arm/configs/s3c6400_defconfig obj.s3c
$ cp arch/arm/configs/spear3xx_defconfig obj.spear
$ cp arch/arm/configs/tegra_defconfig obj.tegra
$ ARCH=arm CROSS_COMPILE=arm-linux-gnu- make -j12 O=obj.dove
$ ARCH=arm CROSS_COMPILE=arm-linux-gnu- make -j12 O=obj.imx
$ ARCH=arm CROSS_COMPILE=arm-linux-gnu- make -j12 O=obj.s3c
$ ARCH=arm CROSS_COMPILE=arm-linux-gnu- make -j12 O=obj.spear
$ ARCH=arm CROSS_COMPILE=arm-linux-gnu- make -j12 O=obj.tegra
There's also sdhci-sirf, but it has its own architecture.
Thanks,
- Chris.
--
Chris Ball <cjb@laptop.org> <http://printf.net/>
next prev parent reply other threads:[~2013-10-21 11:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-16 16:20 [PATCH 0/8] sdhci: Move real work out of an atomic context Jeremie Samuel
2013-10-16 16:20 ` [PATCH 1/8] sdhci: Turn timeout timer into delayed work Jeremie Samuel
2013-10-16 16:20 ` [PATCH 2/8] sdhci: Turn tuning " Jeremie Samuel
2013-10-16 16:20 ` [PATCH 3/8] sdhci: Use work structs instead of tasklets Jeremie Samuel
2013-10-21 1:49 ` Chris Ball
2013-10-21 8:36 ` Jeremie Samuel
2013-10-21 11:44 ` Chris Ball [this message]
2013-10-16 16:20 ` [PATCH 4/8] sdhci: Use threaded IRQ handler Jeremie Samuel
2013-10-16 16:20 ` [PATCH 5/8] sdhci: Delay led blinking Jeremie Samuel
2013-10-16 16:20 ` [PATCH 6/8] sdhci: Turn host->lock into a mutex Jeremie Samuel
2013-10-16 16:20 ` [PATCH 7/8] sdhci: Get rid of mdelay()s where it is safe and makes sense Jeremie Samuel
2013-10-16 16:20 ` [PATCH 8/8] sdhci: Use jiffies instead of a timeout counter Jeremie Samuel
-- strict thread matches above, loose matches on Subject: below --
2013-07-09 15:44 [PATCH 0/8] sdhci: Move real work out of an atomic context Jeremie Samuel
2013-07-09 15:44 ` [PATCH 3/8] sdhci: Use work structs instead of tasklets Jeremie Samuel
2013-05-24 16:00 [PATCH 0/8] sdhci: Move real work out of an atomic context Jeremie Samuel
2013-05-24 16:00 ` [PATCH 3/8] sdhci: Use work structs instead of tasklets Jeremie Samuel
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=86li1mq25n.fsf@void.printf.net \
--to=cjb@laptop.org \
--cc=avorontsov@mvista.com \
--cc=gregor.boirie@parrot.com \
--cc=jeremie.samuel.ext@parrot.com \
--cc=linux-mmc@vger.kernel.org \
--cc=matthieu.castet@parrot.com \
/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).