From: Samuel Ortiz <sameo@linux.intel.com>
To: Peter Ujfalusi <peter.ujfalusi@ti.com>
Cc: Tony Lindgren <tony@atomide.com>, Liam Girdwood <lrg@ti.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org,
linux-next@vger.kernel.org, paul.gortmaker@windriver.com
Subject: Re: [PATCH 0/5] MFD: Reverting twl6040 patches going for 3.4
Date: Tue, 6 Mar 2012 18:42:13 +0100 [thread overview]
Message-ID: <20120306174213.GY9008@sortiz-mobl> (raw)
In-Reply-To: <1331037316-7375-1-git-send-email-peter.ujfalusi@ti.com>
Hi Peter,
On Tue, Mar 06, 2012 at 02:35:11PM +0200, Peter Ujfalusi wrote:
> Hello Samuel,
>
> this series reverts the twl6040 related patches aimed for 3.4 merge window from
> MFD for-next branch.
> As we already discussed the relevant patches will be going through audio since
> we have some dependencies going via that route.
I removed all 5 patches from my for-next branch.
Cheers,
Samuel.
--
Intel Open Source Technology Centre
http://oss.intel.com/
prev parent reply other threads:[~2012-03-06 17:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-06 12:35 [PATCH 0/5] MFD: Reverting twl6040 patches going for 3.4 Peter Ujfalusi
2012-03-06 12:35 ` [PATCH 1/5] Revert "mfd/Input/ASoC: twl6040 kconfig fixes" Peter Ujfalusi
2012-03-06 12:35 ` [PATCH 2/5] Revert "mfd: Add regulator support for twl6040 VIO, V2V1 supplies" Peter Ujfalusi
2012-03-06 12:35 ` [PATCH 3/5] Revert "ASoC: Remove twl6040 dependency on twl4030 from Kconfig" Peter Ujfalusi
2012-03-06 12:35 ` [PATCH 4/5] Revert "mfd: Convert twl6040 to an i2c driver, and separate it from twl core" Peter Ujfalusi
2012-03-06 12:35 ` [PATCH 5/5] Revert "mfd: Detach twl6040 from the pmic mfd driver" Peter Ujfalusi
2012-03-06 17:42 ` 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=20120306174213.GY9008@sortiz-mobl \
--to=sameo@linux.intel.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=lrg@ti.com \
--cc=paul.gortmaker@windriver.com \
--cc=peter.ujfalusi@ti.com \
--cc=sfr@canb.auug.org.au \
--cc=tony@atomide.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).