From: alberto@amarulasolutions.com (Alberto Panizzo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv2 0/4] Continue the mx31_3ds machine support
Date: Mon, 07 Mar 2011 11:09:58 +0100 [thread overview]
Message-ID: <1299492598.2468.30.camel@realization> (raw)
Hello,
this series on top of Sascha's imx-for-2.6.39 branch continue the
support of peripherals for the machine mx31_3ds.
The first one fix also a kernel NULL pointer error introduced by
4d2f13be1e370a670c1cae20c194d5ce961e0fa5
In v2 all group of GPIO requests are packed with gpio_request_array
Best regards,
--
| Alberto Panizzo Amarula Solutions BV |
| CTO - Founder Cruquiuskade 47 |
| T. +31(0)851119171 Amsterdam 1018 AM NL |
| F. +31(0)204106211 www.amarulasolutions.com |
next reply other threads:[~2011-03-07 10:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-07 10:09 Alberto Panizzo [this message]
2011-03-07 10:10 ` [PATCH 1/4] spi_imx: Fix misspelled configuration variable SOC_IMX31 Alberto Panizzo
2011-03-07 10:23 ` [PATCHv2 " Alberto Panizzo
2011-03-07 10:11 ` [PATCHv2 2/4] mach-mx31_3ds: Add support for the MMC slot of the personality board Alberto Panizzo
2011-03-07 10:20 ` Marc Kleine-Budde
2011-03-07 10:12 ` [PATCHv2 3/4] mach-mx31_3ds: Add support for framebuffer and LCD Alberto Panizzo
2011-03-07 10:21 ` Marc Kleine-Budde
2011-03-07 10:13 ` [PATCHv2 4/4] mach-mx31_3ds: Add support for the camera device on the personality board Alberto Panizzo
2011-03-07 10:16 ` [PATCHv2 0/4] Continue the mx31_3ds machine support Marc Kleine-Budde
2011-03-07 10:42 ` [PATCHv3 " Alberto Panizzo
2011-03-07 10:44 ` [PATCHv3 1/4] spi_imx: Fix misspelled configuration variable SOC_IMX31 Alberto Panizzo
2011-03-07 10:45 ` [PATCHv3 2/4] mach-mx31_3ds: Add support for the MMC slot of the personality board Alberto Panizzo
2011-03-07 10:46 ` [PATCHv3 3/4] mach-mx31_3ds: Add support for framebuffer and LCD Alberto Panizzo
2011-03-07 10:47 ` [PATCHv3 4/4] mach-mx31_3ds: Add support for the camera device on the personality board Alberto Panizzo
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=1299492598.2468.30.camel@realization \
--to=alberto@amarulasolutions.com \
--cc=linux-arm-kernel@lists.infradead.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).