From: Kevin Hilman <khilman@deeprootsystems.com>
To: "Shilimkar, Santosh" <santosh.shilimkar@ti.com>
Cc: "Menon, Nishanth" <nm@ti.com>,
"Aguirre, Sergio" <saaguirre@ti.com>,
"Pandita, Vikram" <vikram.pandita@ti.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: FEATURES - is it good enough
Date: Fri, 20 Nov 2009 10:35:39 -0800 [thread overview]
Message-ID: <87eint3uys.fsf@deeprootsystems.com> (raw)
In-Reply-To: <EAF47CD23C76F840A9E7FCE10091EFAB02BBC43A27@dbde02.ent.ti.com> (Santosh Shilimkar's message of "Fri\, 20 Nov 2009 22\:36\:54 +0530")
"Shilimkar, Santosh" <santosh.shilimkar@ti.com> writes:
[...]
>> >
>> > Probably not something ot be attached in this patch, but...
>> >
>> > I'm a bit curious about something:
>> >
>> > Why touching omap3_features in OMAP4?
>> >
>> > Isn't there a omap4_features?
>> >
>> > Or even better, an omap_features?
>
> This "is_feature" suppose to take care of Errata's also, is it?
"It's not a bug it's a feature." :)
> This is errata more than a feature..... We better differentiate in
> this regard
I agree, I have a hard time calling this empty fifo read fault a
"feature." We need a similar thing for errata.
Kevin
next prev parent reply other threads:[~2009-11-20 18:35 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-20 16:02 [PATCH v3 0/2] omap: serial: handle abort on empty rx fifo read Vikram Pandita
2009-11-20 16:02 ` [PATCH v3 1/2] omap: introduce uart_no_empty_fifo_read feature Vikram Pandita
2009-11-20 16:02 ` [PATCH v3 2/2] omap: serial: fix non-empty uart fifo read abort Vikram Pandita
2009-11-20 16:09 ` [PATCH v3 1/2] omap: introduce uart_no_empty_fifo_read feature Nishanth Menon
2009-11-20 16:14 ` Aguirre, Sergio
2009-11-20 16:16 ` FEATURES - is it good enough (was Re: [PATCH v3 1/2] omap: introduce uart_no_empty_fifo_read feature) Nishanth Menon
2009-11-20 17:06 ` Shilimkar, Santosh
2009-11-20 18:35 ` Kevin Hilman [this message]
2009-11-20 19:24 ` FEATURES - is it good enough Nishanth Menon
2009-11-20 19:41 ` Premi, Sanjeev
2009-11-20 19:43 ` Aguirre, Sergio
2009-11-20 20:07 ` Ramirez Luna, Omar
2009-11-20 20:13 ` Aguirre, Sergio
2009-11-20 20:09 ` Nishanth Menon
2009-12-01 15:42 ` Alexander Shishkin
2009-12-02 6:06 ` Menon, Nishanth
2009-12-02 9:05 ` Alexander Shishkin
2009-12-01 13:20 ` [PATCH v3 0/2] omap: serial: handle abort on empty rx fifo read Gadiyar, Anand
2009-12-01 16:05 ` Alexander Shishkin
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=87eint3uys.fsf@deeprootsystems.com \
--to=khilman@deeprootsystems.com \
--cc=linux-omap@vger.kernel.org \
--cc=nm@ti.com \
--cc=saaguirre@ti.com \
--cc=santosh.shilimkar@ti.com \
--cc=vikram.pandita@ti.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 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.