From: Igor Grinberg <grinberg@compulab.co.il>
To: Venu Byravarasu <vbyravarasu@nvidia.com>
Cc: Samuel Ortiz <sameo@linux.intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"jedu@slimlogic.co.uk" <jedu@slimlogic.co.uk>,
"lrg@slimlogic.co.uk" <lrg@slimlogic.co.uk>,
"broonie@opensource.wolfsonmicro.com"
<broonie@opensource.wolfsonmicro.com>,
"gg@slimlogic.co.uk" <gg@slimlogic.co.uk>
Subject: Re: [PATCH] mfd: Fix compilation error in TPS65910.h
Date: Tue, 20 Mar 2012 12:49:19 +0200 [thread overview]
Message-ID: <4F6860AF.5060404@compulab.co.il> (raw)
In-Reply-To: <D958900912E20642BCBC71664EFECE3E6DD3127A5D@BGMAIL02.nvidia.com>
On 03/19/12 10:43, Venu Byravarasu wrote:
> Thanks Mark and Samuel.
>
>> -----Original Message-----
>> From: Samuel Ortiz [mailto:sameo@linux.intel.com]
>> Sent: Saturday, March 17, 2012 1:32 AM
>> To: Venu Byravarasu
>> Cc: linux-kernel@vger.kernel.org; jedu@slimlogic.co.uk; lrg@slimlogic.co.uk;
>> broonie@opensource.wolfsonmicro.com; gg@slimlogic.co.uk
>> Subject: Re: [PATCH] mfd: Fix compilation error in TPS65910.h
>>
>> Hi Venu,
>>
>> On Fri, Mar 16, 2012 at 12:58:37PM +0530, Venu Byravarasu wrote:
>>> From: Venu Byravarasu <vbyravarasu@nvidia.com>
>>>
>>> Fix compilation error due to including TPS65910.h
>> Probably too late for 3.3, but I applied this patch anyway.
Venu,
Should this go also to stable?
If it should then, Samuel, can you please add Cc: stable@vger.kernel.org?
--
Regards,
Igor.
next prev parent reply other threads:[~2012-03-20 10:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-16 7:28 [PATCH] mfd: Fix compilation error in TPS65910.h Venu Byravarasu
2012-03-16 19:02 ` Mark Brown
2012-03-16 20:01 ` Samuel Ortiz
2012-03-19 8:43 ` Venu Byravarasu
2012-03-20 10:49 ` Igor Grinberg [this message]
2012-03-21 5:27 ` Venu Byravarasu
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=4F6860AF.5060404@compulab.co.il \
--to=grinberg@compulab.co.il \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=gg@slimlogic.co.uk \
--cc=jedu@slimlogic.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=lrg@slimlogic.co.uk \
--cc=sameo@linux.intel.com \
--cc=vbyravarasu@nvidia.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