devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nishanth Menon <nm@ti.com>
To: Jassi Brar <jassisinghbrar@gmail.com>
Cc: Mark Rutland <mark.rutland@arm.com>,
	Rob Herring <robh+dt@kernel.org>, Suman Anna <s-anna@ti.com>,
	Tero Kristo <t-kristo@ti.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Devicetree List <devicetree@vger.kernel.org>, ",
	linux-arm-kernel@lists.infradead.org,
	linux-mediatek@lists.infradead.org,
	srv_heupstream" <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH V2 0/6] mailbox: ti-msgmgr: Add support for AM654 Secure Proxy
Date: Mon, 23 Jul 2018 09:14:12 -0500	[thread overview]
Message-ID: <20180723141412.7zd6wp6y6pql7bm7@kahuna> (raw)
In-Reply-To: <CABb+yY1_SBTDPyUNGSr8=tpU4oObz060nJ3NrgR8JyQye23cfg@mail.gmail.com>

On 13:56-20180723, Jassi Brar wrote:
> On Mon, Jul 23, 2018 at 6:59 PM, Nishanth Menon <nm@ti.com> wrote:
[...]
> >>  .../bindings/mailbox/ti,secure-proxy.txt           |  50 +++
> >>  drivers/mailbox/ti-msgmgr.c                        | 353 +++++++++++++++++----
> >>  2 files changed, 336 insertions(+), 67 deletions(-)
> >>  create mode 100644 Documentation/devicetree/bindings/mailbox/ti,secure-proxy.txt
> >
> >
> > Jassi,
> >
> > I dont see this in next-20180723. You'd asked me to hold off on pings
> > https://lkml.org/lkml/2017/12/16/353 -> so, held off as much as I could
> > before wondering on the status.
> >
> I didn't ask you to not ping me. I said I didn't miss your patchset. I
> still didn't.
> 
> Especially for purely platform specific changes, that I don't have
> knowledge about, I leave them to cook in public as long as possible,
> before pulling them in around rc7.

Understood. Thanks.

> You submitted V2, 7days ago only and we are at rc6 today. So chill.

v2 is just wording of mailbox node example change recommended by Rob.
I was hoping to get any further changes prior to reposting a v2.. but
anyways.. Looks all good..

-- 
Regards,
Nishanth Menon

      reply	other threads:[~2018-07-23 14:14 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-16 18:06 [PATCH V2 0/6] mailbox: ti-msgmgr: Add support for AM654 Secure Proxy Nishanth Menon
2018-07-16 18:06 ` [PATCH V2 1/6] mailbox: ti-msgmgr: Get rid of unused structure members Nishanth Menon
2018-07-16 18:06 ` [PATCH V2 2/6] mailbox: ti-msgmgr: Allocate Rx channel resources only on request Nishanth Menon
2018-07-16 18:06 ` [PATCH V2 3/6] mailbox: ti-msgmgr: Change message count mask to be descriptor based Nishanth Menon
2018-07-16 18:06 ` [PATCH V2 4/6] mailbox: ti-msgmgr: Move the memory region name to descriptor Nishanth Menon
2018-07-16 18:06 ` [PATCH V2 5/6] dt-bindings: mailbox: Add support for secure proxy threads Nishanth Menon
2018-07-16 18:06 ` [PATCH V2 6/6] mailbox: ti-msgmgr: Add support for Secure Proxy Nishanth Menon
2018-07-23 13:29 ` [PATCH V2 0/6] mailbox: ti-msgmgr: Add support for AM654 " Nishanth Menon
2018-07-23 13:56   ` Jassi Brar
2018-07-23 14:14     ` Nishanth Menon [this message]

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=20180723141412.7zd6wp6y6pql7bm7@kahuna \
    --to=nm@ti.com \
    --cc=devicetree@vger.kernel.org \
    --cc=jassisinghbrar@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=robh+dt@kernel.org \
    --cc=s-anna@ti.com \
    --cc=t-kristo@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 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).