linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: b-cousson@ti.com (Cousson, Benoit)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/6] [v2] omap:mailbox-enhancements and fixes
Date: Wed, 10 Nov 2010 20:02:35 +0100	[thread overview]
Message-ID: <4CDAEC4B.3000308@ti.com> (raw)
In-Reply-To: <AANLkTi=jL-aV0Xn3rcnZwaYLz9nY5QwXbGPHsdq1R2Gz@mail.gmail.com>

On 11/10/2010 5:56 PM, Hari Kanigeri wrote:

[...]

> Good point, thanks for pointing about consistency. I wasn't aware
> about the rule to use OMAP in caps.

Well, I'm not sure there is any rule like that, it is just what was 
mostly used so far. My point was more about the text after the omap.

Benoit

  parent reply	other threads:[~2010-11-10 19:02 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-10 12:45 [PATCH 0/6] [v2] omap:mailbox-enhancements and fixes Hari Kanigeri
2010-11-10 12:45 ` [PATCH 1/6] mailbox: change full flag per mailbox queue instead of global Hari Kanigeri
2010-11-10 12:45 ` [PATCH 2/6] omap:mailbox: fix rx interrupt disable in omap4 Hari Kanigeri
2010-11-10 12:45 ` [PATCH 3/6] omap:mailbox-fix checkpatch warnings Hari Kanigeri
2010-11-10 16:49   ` Sergei Shtylyov
2010-11-10 12:45 ` [PATCH 4/6] omap:mailbox-send message in process context Hari Kanigeri
2010-11-10 12:45 ` [PATCH 5/6] omap:mailbox-add notification support for multiple readers Hari Kanigeri
2010-11-10 12:45 ` [PATCH 6/6] omap:clocks44x-add dummy clock for mailbox Hari Kanigeri
2010-11-10 23:27   ` Paul Walmsley
2010-11-11  1:37     ` Hari Kanigeri
2010-11-10 16:40 ` [PATCH 0/6] [v2] omap:mailbox-enhancements and fixes Cousson, Benoit
2010-11-10 16:56   ` Hari Kanigeri
2010-11-10 18:58     ` Cousson, Benoit
2010-11-10 19:17       ` Felipe Balbi
2010-11-10 19:02     ` Cousson, Benoit [this message]
2010-11-10 16:52 ` Cousson, Benoit

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=4CDAEC4B.3000308@ti.com \
    --to=b-cousson@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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).