From: Samuel Ortiz <sameo@linux.intel.com>
To: Afzal Mohammed <afzal@ti.com>
Cc: linux-kernel@vger.kernel.org,
broonie@opensource.wolfsonmicro.com, lrg@ti.com, nsekhar@ti.com,
linux-omap@vger.kernel.org
Subject: Re: [PATCH RESEND v2 0/2] PMIC TPS65910 fixes
Date: Mon, 12 Dec 2011 12:46:18 +0100 [thread overview]
Message-ID: <20111212114618.GB13952@sortiz-mobl> (raw)
In-Reply-To: <1320758615-29085-1-git-send-email-afzal@ti.com>
Hi Mohamed,
On Tue, Nov 08, 2011 at 06:53:35PM +0530, Afzal Mohammed wrote:
> Hi,
>
> This series applies over Kyle Manna's v3 patch series,
> https://lkml.org/lkml/2011/11/3/257,
> with changes as per comments on
> his/her 1/6 "mfd: TPS65910: Handle non-existent devices"
Kyle has not updated the patchset, afaik. So your patches don't apply on top
of my for-next branch. Please rebase them.
Cheers,
Samuel.
--
Intel Open Source Technology Centre
http://oss.intel.com/
prev parent reply other threads:[~2011-12-12 11:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-08 13:23 [PATCH RESEND v2 0/2] PMIC TPS65910 fixes Afzal Mohammed
2011-12-12 11:46 ` Samuel Ortiz [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=20111212114618.GB13952@sortiz-mobl \
--to=sameo@linux.intel.com \
--cc=afzal@ti.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=lrg@ti.com \
--cc=nsekhar@ti.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