From: Benoit Cousson <b-cousson@ti.com>
To: "Hiremath, Vaibhav" <hvaibhav@ti.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"devicetree-discuss@lists.ozlabs.org"
<devicetree-discuss@lists.ozlabs.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Tony Lindgren <tony@atomide.com>, Paul Walmsley <paul@pwsan.com>,
"Hilman, Kevin" <khilman@ti.com>
Subject: Re: [RFC PATCH] ARM: OMAP2+: omap-device: Do not overwrite resources allocated by OF layer
Date: Fri, 31 Aug 2012 17:42:01 +0200 [thread overview]
Message-ID: <5040DB49.9000403@ti.com> (raw)
In-Reply-To: <79CD15C6BA57404B839C016229A409A83EA9EA8E@DBDE01.ent.ti.com>
On 08/31/2012 05:36 PM, Hiremath, Vaibhav wrote:
> On Fri, Aug 31, 2012 at 20:54:53, Cousson, Benoit wrote:
...
> I think you are getting confused between Vaibhav B and Vaibhav H :)
> We have two Vaibhav's roaming around here ;-)
Oops, sorry, this is the very first time I realized that two different
Vaibhav were sending patches on very similar topic...
That's why you were so good generating a lot of patches :-) You have a
dual channel of patches :-)
> I was not there during LPC this time, it was Vaibhav B who attended it.
> I will sync up with him and try to get more info on it.
Sorry again for the confusion.
Thanks,
Benoit
next prev parent reply other threads:[~2012-08-31 15:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-29 9:48 [RFC PATCH] ARM: OMAP2+: omap-device: Do not overwrite resources allocated by OF layer Vaibhav Hiremath
2012-08-31 15:24 ` Benoit Cousson
2012-08-31 15:36 ` Hiremath, Vaibhav
2012-08-31 15:42 ` Benoit Cousson [this message]
2012-09-05 9:20 ` Peter Ujfalusi
2012-09-07 17:47 ` Benoit Cousson
[not found] ` <504A3339.1020506-l0cyMroinI0@public.gmane.org>
2012-09-07 18:44 ` Hiremath, Vaibhav
2012-09-07 18:03 ` Benoit Cousson
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=5040DB49.9000403@ti.com \
--to=b-cousson@ti.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=hvaibhav@ti.com \
--cc=khilman@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.com \
--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).