From: Samuel Ortiz <sameo@linux.intel.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
Mark Brown <broonie@opensource.wolfsonmicro.com>
Subject: [GIT] [2.6.34] MFD fixes
Date: Thu, 13 May 2010 16:00:48 +0200 [thread overview]
Message-ID: <20100513140045.GA23349@sortiz.org> (raw)
Hi Linus,
Sorry for being late, I just got back from a (way earlier than expected)
paternity leave. I have one MFD fix pending for 2.6.34, I'd appreciate if you
could still pull:
The following changes since commit be835674b55324c1abe973b15343c3663910c620:
Linus Torvalds (1):
Merge branch 'merge' of git://git.kernel.org/.../benh/powerpc
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/sameo/mfd-2.6.git for-linus
Mark Brown (1):
mfd: Clean up after WM83xx AUXADC interrupt if it arrives late
drivers/mfd/wm831x-core.c | 3 +++
drivers/mfd/wm8350-core.c | 4 ++++
2 files changed, 7 insertions(+), 0 deletions(-)
--
Intel Open Source Technology Centre
http://oss.intel.com/
reply other threads:[~2010-05-13 14:00 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20100513140045.GA23349@sortiz.org \
--to=sameo@linux.intel.com \
--cc=broonie@opensource.wolfsonmicro.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox