Re: [PATCHv7 0/5] Common Mailbox Framework

On 30 June 2014 21:46, Lubomir Rintel wrote: > Hi Jassi, > > On Thu, 2014-06-12 at 22:28 +0530, Jassi Brar wrote: >> Hello, >> Here is the next revision of Mailbox framwork. > > I'm wondering whether you keep a Git tree with the framework we could > keep the Raspberry Pi mailbox driver based on

Re: [PATCHv7 0/5] Common Mailbox Framework

Hi Jassi, On Thu, 2014-06-12 at 22:28 +0530, Jassi Brar wrote: > Hello, > Here is the next revision of Mailbox framwork. I'm wondering whether you keep a Git tree with the framework we could keep the Raspberry Pi mailbox driver based on (bcm2835-mbox)? Also, from look at the API it does not

Re: [PATCHv7 0/5] Common Mailbox Framework

Hi Jassi, On Thu, 2014-06-12 at 22:28 +0530, Jassi Brar wrote: Hello, Here is the next revision of Mailbox framwork. I'm wondering whether you keep a Git tree with the framework we could keep the Raspberry Pi mailbox driver based on (bcm2835-mbox)? Also, from look at the API it does not

Re: [PATCHv7 0/5] Common Mailbox Framework

On 30 June 2014 21:46, Lubomir Rintel lkund...@v3.sk wrote: Hi Jassi, On Thu, 2014-06-12 at 22:28 +0530, Jassi Brar wrote: Hello, Here is the next revision of Mailbox framwork. I'm wondering whether you keep a Git tree with the framework we could keep the Raspberry Pi mailbox driver

[PATCHv7 0/5] Common Mailbox Framework

Hello, Here is the next revision of Mailbox framwork. Changes since v6: o Separate out generic DT bindings patch. o Discard unnecessary aligned attributes. Changes since v5: o Use standard error types instead of special type mbox_result. o Constify client struct in request_channel o Use

[PATCHv7 0/5] Common Mailbox Framework

Hello, Here is the next revision of Mailbox framwork. Changes since v6: o Separate out generic DT bindings patch. o Discard unnecessary aligned attributes. Changes since v5: o Use standard error types instead of special type mbox_result. o Constify client struct in request_channel o Use