From: Nishanth Menon <nm@ti.com>
To: Venkatraman S <svenkatr@ti.com>
Cc: Nishanth Menon <menon.nishanth@gmail.com>,
linux omap <linux-omap@vger.kernel.org>,
Tony Lindgren <tony@atomide.com>,
Angelo Arrifano <miknix@gmail.com>,
"Zebediah C. McClure" <zmc@lurian.net>,
Alistair Buxton <a.j.buxton@gmail.com>,
Paul Walmsley <paul@pwsan.com>, "Premi, Sanjeev" <premi@ti.com>,
"Shilimkar, Santosh" <santosh.shilimkar@ti.com>,
"Guruswamy, Senthilvadivu" <svadivu@ti.com>,
Kevin Hilman <khilman@deeprootsystems.com>,
Tomi Valkeinen <tomi.valkeinen@nokia.com>,
Aaro Koskinen <aaro.koskinen@nokia.com>,
"Pandita, Vikram" <vikram.pandita@ti.com>,
"S, Vishwanath" <vishwa.s@ti.com>
Subject: Re: [PATCH 6/6] omap: move generic omap3 features to generic
Date: Tue, 1 Jun 2010 09:23:24 +0300 [thread overview]
Message-ID: <4C04A75C.6080709@ti.com> (raw)
In-Reply-To: <AANLkTilLDPZqmFfVbey0aFixbWRZ4lyAklTuvu5Kv84A@mail.gmail.com>
On 06/01/2010 08:34 AM, Venkatraman S wrote:
> If you can post them formally as part of the series, I can test and
> ack them (with OMAP3, OMAP4)
> My original comment was even if these were not implemented due to some
> constraints, they should be
> mentioned in the code (as TODO / FIXME etc). The caveat description is
> not going to show up in
> commit logs or printks
okie.. the 3 RFC patches following to the list.
Regards,
Nishanth Menon
prev parent reply other threads:[~2010-06-01 6:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-23 3:36 [PATCH 0/6] introduce generic OMAP SOC features Nishanth Menon
2010-05-23 3:36 ` [PATCH 1/6] omap1: rename check_revision Nishanth Menon
2010-05-23 3:36 ` [PATCH 2/6] omap2/3: id: fix sparse warning Nishanth Menon
2010-05-23 3:36 ` [PATCH 3/6] omap: generic: introduce a single check_revision Nishanth Menon
2010-05-23 3:36 ` [PATCH 4/6] omap: improve OMAP3_HAS_FEATURE Nishanth Menon
2010-05-23 3:36 ` [PATCH 5/6] omap: introduce OMAP_SHOW_FEATURE Nishanth Menon
2010-05-23 3:36 ` [PATCH 6/6] omap: move generic omap3 features to generic Nishanth Menon
2010-05-27 11:24 ` Venkatraman S
2010-05-27 16:21 ` Nishanth Menon
2010-05-31 16:06 ` Venkatraman S
2010-05-31 17:09 ` Nishanth Menon
2010-05-31 18:46 ` Venkatraman S
2010-05-31 19:18 ` Nishanth Menon
2010-06-01 5:34 ` Venkatraman S
2010-06-01 6:23 ` Nishanth Menon [this message]
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=4C04A75C.6080709@ti.com \
--to=nm@ti.com \
--cc=a.j.buxton@gmail.com \
--cc=aaro.koskinen@nokia.com \
--cc=khilman@deeprootsystems.com \
--cc=linux-omap@vger.kernel.org \
--cc=menon.nishanth@gmail.com \
--cc=miknix@gmail.com \
--cc=paul@pwsan.com \
--cc=premi@ti.com \
--cc=santosh.shilimkar@ti.com \
--cc=svadivu@ti.com \
--cc=svenkatr@ti.com \
--cc=tomi.valkeinen@nokia.com \
--cc=tony@atomide.com \
--cc=vikram.pandita@ti.com \
--cc=vishwa.s@ti.com \
--cc=zmc@lurian.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.