From: "Cousson, Benoit" <b-cousson@ti.com>
To: Hari Kanigeri <h-kanigeri2@ti.com>
Cc: Hiroshi Doyu <Hiroshi.DOYU@nokia.com>,
linux omap <linux-omap@vger.kernel.org>,
Tony Lindgren <tony@atomide.com>,
Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 0/6] [v2] omap:mailbox-enhancements and fixes
Date: Wed, 10 Nov 2010 17:40:46 +0100 [thread overview]
Message-ID: <4CDACB0E.3050403@ti.com> (raw)
In-Reply-To: <1289393121-7911-1-git-send-email-h-kanigeri2@ti.com>
Hi Hari,
On 11/10/2010 1:45 PM, Hari Kanigeri wrote:
> Thanks to Rene Sapiens and Omar Ramirez for their inputs on initial patch
> set.
> http://www.mail-archive.com/linux-omap@vger.kernel.org/msg37278.html
>
> The patch set addresses the following review comments from Rene and Omar.
> http://www.mail-archive.com/linux-omap@vger.kernel.org/msg37626.html
> https://patchwork.kernel.org/patch/255091/
> https://patchwork.kernel.org/patch/255081/
>
> Following patches are changed because of above review comments:
> omap:mailbox-send message in process context
> omap:mailbox-add notification support for multiple readers
>
> Following patch is dropped from initial patch set
> omap:mailbox-resolve multiple receiver problem
>
> The patch set is tested on omap4 SDP board.
>
> Fernando Guzman Lugo (1):
> mailbox: change full flag per mailbox queue instead of global
>
> Hari Kanigeri (5):
> omap:mailbox: fix rx interrupt disable in omap4
> omap:mailbox-fix checkpatch warnings
That one is weird? How can you submit a patch that fix checkpatch?
In theory you should not send any patch that generate checkpatch error
or warning.
> omap:mailbox-send message in process context
> omap:mailbox-add notification support for multiple readers
> omap:clocks44x-add dummy clock for mailbox
We are trying to enforce some consistency in the subjects name so you
should name your patches like that:
OMAP: mailbox: fix rx interrupt disable in omap4
OMAP: mailbox: fix checkpatch warnings
OMAP: mailbox: send message in process context
OMAP: mailbox: add notification support for multiple readers
OMAP4: clocks: add dummy clock for mailbox
Regards,
Benoit
next prev parent reply other threads:[~2010-11-10 16:40 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 ` Cousson, Benoit [this message]
2010-11-10 16:56 ` [PATCH 0/6] [v2] omap:mailbox-enhancements and fixes Hari Kanigeri
2010-11-10 18:58 ` Cousson, Benoit
2010-11-10 19:17 ` Felipe Balbi
2010-11-10 19:02 ` Cousson, Benoit
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=4CDACB0E.3050403@ti.com \
--to=b-cousson@ti.com \
--cc=Hiroshi.DOYU@nokia.com \
--cc=h-kanigeri2@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--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