From: Tony Lindgren <tony@atomide.com>
To: Grant Likely <grant.likely@secretlab.ca>
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: Thu, 18 Feb 2010 09:09:47 -0800 [thread overview]
Message-ID: <20100218170946.GO21755@atomide.com> (raw)
In-Reply-To: <fa686aa41002180828l378a9550u125752e1e972a345@mail.gmail.com>
* Grant Likely <grant.likely@secretlab.ca> [100218 08:26]:
> 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>
>
> Tony, do you want me to add your acked-by to patches 2 & 3?
No thanks, I've only looked at them briefly.
> Also, what is your feeling about patch 3/3, spi slave support. spi
> slave usage model is still a matter under debate, but that patch
> doesn't touch core spi code, so I'm okay to merge it as a
> driver-specific feature. However, I'm not convinced that it is
> actually a useful patch to merge yet, so I'll defer to you on this
> one. Thoughts?
Up to you to decide. But here's my experience so far..
Based on my experience if temporary hacks are merged, then nobody
bothers to clean them up properly afterwards and the clean-up task
unfairly falls on the maintainer.
So IMHO, hacks like that are better floating on the mailing list
until they're properly done. It's best to concentrate on getting
the core things done right to make long term support easier.
Regards,
Tony
next prev parent reply other threads:[~2010-02-18 17:09 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
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 [this message]
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=20100218170946.GO21755@atomide.com \
--to=tony@atomide.com \
--cc=dbrownell@users.sourceforge.net \
--cc=grant.likely@secretlab.ca \
--cc=hemanthv@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=spi-devel-general@lists.sourceforge.net \
/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).