linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: omar.ramirez@copitl.com (Omar Ramirez Luna)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/9] mailbox: OMAP: introduce mailbox framework
Date: Fri, 11 Jan 2013 07:34:12 -0600	[thread overview]
Message-ID: <CAJ6Av5M==RCCc-ngKMebPgqUwVT5Gr7E=NNk4Rr2OQK5TzfORQ@mail.gmail.com> (raw)
In-Reply-To: <50ED62B3.50000@st.com>

On Wed, Jan 9, 2013 at 6:29 AM, Loic PALLARDY <loic.pallardy@st.com> wrote:
> Hi Vaibhav,
>
> On 01/09/2013 01:11 PM, Bedia, Vaibhav wrote:
>> Hi Loic,
>>
>> On Fri, Dec 21, 2012 at 16:23:24, Loic PALLARDY wrote:
>>>
>>>
>>> On 12/21/2012 11:49 AM, Bedia, Vaibhav wrote:
>>>> On Fri, Dec 21, 2012 at 14:24:26, Loic PALLARDY wrote:
>>>>>
>>>> I have a few patches which are dependent on this patch series.
>>>> Could you please keep me in cc for the future versions.
>>>>
>>> Sure, I'll.
>>>
>>
>> When do you plan to post an updated version of these patches?
> I'm synchronizing with Omar to include TI RPMsg and tidspbridge patches
> in next update.
> So I plan update for end of the week, beginning of next week.

Here are my patches, I didn't post them to the list since they are
meant to be squashed, I also prepared a squashed version of the
original set, in case it is easier to take that one, all rebased into
3.8-rc1. Branches: mailbox-3.8-rc1-separate-changes and
mailbox-3.8-rc1, respectively.

>From tree: https://github.com/omarrmz/upstream-wip

Cheers,

Omar

  parent reply	other threads:[~2013-01-11 13:34 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-18 13:10 [PATCH 0/9] drivers: mailbox: framework creation Loic Pallardy
2012-12-18 13:10 ` [PATCH 1/9] mailbox: OMAP: introduce mailbox framework Loic Pallardy
2012-12-18 16:59   ` Tony Lindgren
2012-12-21  8:54     ` Loic PALLARDY
2012-12-21 10:49       ` Bedia, Vaibhav
2012-12-21 10:53         ` Loic PALLARDY
2013-01-09 12:11           ` Bedia, Vaibhav
2013-01-09 12:29             ` Loic PALLARDY
2013-01-09 12:34               ` Bedia, Vaibhav
2013-01-11 13:34               ` Omar Ramirez Luna [this message]
2012-12-18 13:10 ` [PATCH 2/9] mailbox: split internal header from API header Loic Pallardy
2012-12-18 13:10 ` [PATCH 3/9] mailbox: rename omap_mbox in mailbox Loic Pallardy
2012-12-20 21:29   ` Ohad Ben-Cohen
2012-12-18 13:10 ` [PATCH 4/9] mailbox: create opened message type Loic Pallardy
2012-12-21 10:28   ` Bedia, Vaibhav
2012-12-21 10:50     ` Loic PALLARDY
2012-12-18 13:10 ` [PATCH 5/9] mailbox: change protection mechanisms Loic Pallardy
2012-12-21 10:28   ` Bedia, Vaibhav
2012-12-21 10:50     ` Loic PALLARDY
2012-12-18 13:10 ` [PATCH 6/9] mailbox: add shared memory mailbox type Loic Pallardy
2012-12-18 13:10 ` [PATCH 7/9] mailbox: add IRQF_NO_SUSPEND flag Loic Pallardy
2012-12-18 13:10 ` [PATCH 8/9] mailbox: add no_irq send message Loic Pallardy
2012-12-18 13:10 ` [PATCH 9/9] mailbox: create dbx500 mailbox driver Loic Pallardy
2012-12-20 18:16 ` [PATCH 0/9] drivers: mailbox: framework creation Linus Walleij
2012-12-20 18:28   ` Tony Lindgren
2012-12-20 19:19     ` Olof Johansson
2012-12-20 19:33       ` Tony Lindgren
2012-12-21  7:31       ` Ohad Ben-Cohen
2012-12-21  8:52         ` Loic PALLARDY
2012-12-21 19:33           ` Omar Ramirez Luna
2012-12-24 15:17             ` Ohad Ben-Cohen

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='CAJ6Av5M==RCCc-ngKMebPgqUwVT5Gr7E=NNk4Rr2OQK5TzfORQ@mail.gmail.com' \
    --to=omar.ramirez@copitl.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).