From: Liam Girdwood <lrg@ti.com>
To: "axel.lin@gmail.com" <axel.lin@gmail.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Jin Park <jinyoungp@nvidia.com>,
Mark Brown <broonie@opensource.wolfsonmicro.com>,
Samuel Ortiz <sameo@linux.intel.com>
Subject: Re: [PATCH 1/2 RESEND] regulator: aat2870: Fix the logic of checking if no id is matched in aat2870_get_regulator
Date: Wed, 10 Aug 2011 22:31:25 +0100 [thread overview]
Message-ID: <4E42F8AD.5050000@ti.com> (raw)
In-Reply-To: <CAF+7xWkUO0d7Bp4a8-0cksZhhcQ-jb4XfRCEP=qCqb3_qb5RxQ@mail.gmail.com>
On 10/08/11 16:19, Axel Lin wrote:
> 2011/7/30 Liam Girdwood <lrg@ti.com>:
>> On Fri, 2011-07-29 at 18:05 +0200, Axel Lin wrote:
>>> hi,
>>> Seems this 2 patches are not upstream. Should I resend it again?
>>> Regards,
>>> Axel
>>
>> Not required atm thanks, this driver went via mfd so I can apply the fix
>> after the mfd merge or rc1.
> hi Liam,
> aat2870-regulator.c is already merged to your tree but
> seems these 2 patches are not (yet) upstream.
>
Could you check regulator git #for-linus. I applied a bunch of patches a few days ago and some for this device. I'll do a pull request for rc2 in a few days.
Thanks
Liam
next prev parent reply other threads:[~2011-08-10 21:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-06 23:38 [PATCH 1/2 RESEND] regulator: aat2870: Fix the logic of checking if no id is matched in aat2870_get_regulator Axel Lin
2011-07-06 23:39 ` [PATCH 2/2 RESEND] regulator: aat2870: Remove a redundant bitwise and operation Axel Lin
2011-07-29 16:05 ` [PATCH 1/2 RESEND] regulator: aat2870: Fix the logic of checking if no id is matched in aat2870_get_regulator Axel Lin
2011-07-29 16:10 ` Liam Girdwood
2011-08-10 15:19 ` Axel Lin
2011-08-10 21:31 ` Liam Girdwood [this message]
2011-08-10 23:10 ` Axel Lin
-- strict thread matches above, loose matches on Subject: below --
2011-08-29 14:48 Axel Lin
2011-08-31 13:26 ` Liam Girdwood
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=4E42F8AD.5050000@ti.com \
--to=lrg@ti.com \
--cc=axel.lin@gmail.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=jinyoungp@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sameo@linux.intel.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