From: Grant Likely <grant.likely@secretlab.ca>
To: Tony Lindgren <tony@atomide.com>
Cc: Hemanth V <hemanthv@ti.com>,
spi-devel-general@lists.sourceforge.net,
linux-omap@vger.kernel.org, dbrownell@users.sourceforge.net
Subject: Re: PATCH[V2 1/3]: Update Platform files for SPI
Date: Tue, 9 Feb 2010 15:40:43 -0700 [thread overview]
Message-ID: <fa686aa41002091440p588ad328i14d0fb28390b2672@mail.gmail.com> (raw)
In-Reply-To: <20100209222513.GJ21755@atomide.com>
On Tue, Feb 9, 2010 at 3:25 PM, Tony Lindgren <tony@atomide.com> wrote:
> * Hemanth V <hemanthv@ti.com> [100203 02:19]:
>> From ee48142ddc43129a21676dbb56a83e3e7d8063de Mon Sep 17 00:00:00 2001
>> From: Hemanth V <hemanthv@ti.com>
>> Date: Fri, 27 Nov 2009 14:22:30 +0530
>> Subject: [PATCH] Update platform files
>>
>> This patch updates platform files for
>> fifo, slave support
>>
>> Signed-off-by: Hemanth V <hemanthv@ti.com>
>
> This should get merged via the spi-devel list with the other patches.
>
> Acked-by: Tony Lindgren <tony@atomide.com>
Personally, I prefer not to carry arch/* changes in my next-spi
branch, since it means that my pull requests are less obvious for
Linus and there is greater chance of conflict.
But if you still really want me to merge it through my tree, (or if
getting the patches out of order will break things) then I'll pick it
up. Just let me know.
g.
--
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
next prev parent reply other threads:[~2010-02-09 22:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-03 10:21 PATCH[V2 1/3]: Update Platform files for SPI Hemanth V
2010-02-09 22:25 ` Tony Lindgren
2010-02-09 22:40 ` Grant Likely [this message]
2010-02-09 23:07 ` Tony Lindgren
2010-02-10 0:10 ` Grant Likely
2010-02-10 10:03 ` Hemanth V
2010-02-12 21:48 ` Tony Lindgren
2010-02-16 14:38 ` Hemanth V
2010-02-16 21:02 ` Grant Likely
2010-02-18 16:28 ` Grant Likely
2010-02-18 17:09 ` Tony Lindgren
2010-02-18 17:29 ` Grant Likely
2010-06-30 20:03 ` Grant Likely
[not found] ` <AANLkTinEfJqvRZKqMaXY3_EE4WJT3W3_j0Kwg89pt_SU-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-07-06 9:17 ` Hemanth V
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=fa686aa41002091440p588ad328i14d0fb28390b2672@mail.gmail.com \
--to=grant.likely@secretlab.ca \
--cc=dbrownell@users.sourceforge.net \
--cc=hemanthv@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=spi-devel-general@lists.sourceforge.net \
--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).