From: Samuel Ortiz <sameo@openedhand.com>
To: Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Cc: Mark Brown <broonie@opensource.wolfsonmicro.com>,
Eric Miao <eric.miao@marvell.com>,
Jonathan Cameron <jic23@cam.ac.uk>
Subject: [GIT] mfd pull request
Date: Fri, 24 Oct 2008 19:02:58 +0200 [thread overview]
Message-ID: <20081024170257.GA5528@sortiz.org> (raw)
Hi Linus,
Could you please pull a couple of mfd fixes from:
git://git.o-hand.com/linux-mfd for-linus
The first one fixes a build failure when wm8400 is built in while i2c is a
module.
The second fix adds a left out Kconfig entry for da903x.
Cheers,
Samuel.
The following changes since commit e013e13bf605b9e6b702adffbe2853cfc60e7806:
Jens Axboe (1):
libata: fix bug with non-ncq devices
are available in the git repository at:
git://git.o-hand.com/linux-mfd for-linus
Mark Brown (1):
mfd: Make WM8400 depend on I2C until SPI is submitted
Samuel Ortiz (1):
mfd: add missing Kconfig entry for da903x
drivers/mfd/Kconfig | 12 ++++++++++++
drivers/mfd/Makefile | 2 ++
2 files changed, 14 insertions(+), 0 deletions(-)
--
Intel Open Source Technology Centre
http://oss.intel.com/
next reply other threads:[~2008-10-24 17:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-24 17:02 Samuel Ortiz [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-10-12 14:53 [GIT] MFD pull request Samuel Ortiz
2009-04-04 23:07 Samuel Ortiz
[not found] <20090331113648.GA4612@sortiz.org>
2009-03-31 13:34 ` Samuel Ortiz
2009-02-17 8:47 Samuel Ortiz
2009-01-11 13:43 Samuel Ortiz
2009-01-04 23:15 Samuel Ortiz
2008-10-22 9:44 [GIT] mfd " Samuel Ortiz
2008-10-19 21:49 Samuel Ortiz
2008-10-16 10:10 Samuel Ortiz
2008-09-30 8:19 [GIT] MFD " Samuel Ortiz
2008-07-29 0:02 Samuel Ortiz
2008-07-20 23:24 Samuel Ortiz
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=20081024170257.GA5528@sortiz.org \
--to=sameo@openedhand.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=eric.miao@marvell.com \
--cc=jic23@cam.ac.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.