From: Jassi Brar <jassisinghbrar@gmail.com>
To: Daniel Baluta <daniel.baluta@gmail.com>
Cc: Richard Zhu <hongxing.zhu@nxp.com>,
Oleksij Rempel <o.rempel@pengutronix.de>,
Daniel Baluta <daniel.baluta@nxp.com>,
Aisheng Dong <aisheng.dong@nxp.com>,
dl-linux-imx <linux-imx@nxp.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
Shawn Guo <shawnguo@kernel.org>
Subject: Re: [RESEND PATCH v5 4/4] mailbox: imx: add support for imx v1 mu
Date: Tue, 29 Oct 2019 16:02:03 -0500 [thread overview]
Message-ID: <CABb+yY1-PrmT_Qp6M1+WTnVAKizVqJLYJcip4KfqcAjcuN3GCg@mail.gmail.com> (raw)
In-Reply-To: <CAEnQRZDk4TjU0nWgGXEV06ZygvSyuPHc61_uT7KRu0j2Aaxj7w@mail.gmail.com>
On Tue, Oct 29, 2019 at 4:07 AM Daniel Baluta <daniel.baluta@gmail.com> wrote:
>
> Since we got no answer from Jassi in 4 months I think it is safe
> to assume that we can get this through Shawn's tree.
>
Please don't top post.
This patchset doesn't lack my love. It contains support for a new
platform and was sent after last merge window. I send new
features/support only for next release. If you want some urgent
bugfixes picked , please send them separately.
Cheers!
WARNING: multiple messages have this Message-ID (diff)
From: Jassi Brar <jassisinghbrar@gmail.com>
To: Daniel Baluta <daniel.baluta@gmail.com>
Cc: Aisheng Dong <aisheng.dong@nxp.com>,
Richard Zhu <hongxing.zhu@nxp.com>,
Shawn Guo <shawnguo@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Oleksij Rempel <o.rempel@pengutronix.de>,
dl-linux-imx <linux-imx@nxp.com>,
Daniel Baluta <daniel.baluta@nxp.com>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>
Subject: Re: [RESEND PATCH v5 4/4] mailbox: imx: add support for imx v1 mu
Date: Tue, 29 Oct 2019 16:02:03 -0500 [thread overview]
Message-ID: <CABb+yY1-PrmT_Qp6M1+WTnVAKizVqJLYJcip4KfqcAjcuN3GCg@mail.gmail.com> (raw)
In-Reply-To: <CAEnQRZDk4TjU0nWgGXEV06ZygvSyuPHc61_uT7KRu0j2Aaxj7w@mail.gmail.com>
On Tue, Oct 29, 2019 at 4:07 AM Daniel Baluta <daniel.baluta@gmail.com> wrote:
>
> Since we got no answer from Jassi in 4 months I think it is safe
> to assume that we can get this through Shawn's tree.
>
Please don't top post.
This patchset doesn't lack my love. It contains support for a new
platform and was sent after last merge window. I send new
features/support only for next release. If you want some urgent
bugfixes picked , please send them separately.
Cheers!
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-10-29 21:02 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-05 4:52 [PATCH v5 0/4] mailbox: imx: bug fix and add support for imx v1 mu Richard Zhu
2019-08-05 4:52 ` Richard Zhu
2019-08-05 4:52 ` [RESEND PATCH v5 1/4] mailbox: imx: Fix Tx doorbell shutdown path Richard Zhu
2019-08-05 4:52 ` Richard Zhu
2019-08-05 4:52 ` [RESEND PATCH v5 2/4] mailbox: imx: Clear the right interrupts at shutdown Richard Zhu
2019-08-05 4:52 ` Richard Zhu
2019-08-05 4:52 ` [RESEND PATCH v5 3/4] dt-bindings: mailbox: imx-mu: add imx7ulp MU support Richard Zhu
2019-08-05 4:52 ` Richard Zhu
2019-08-05 19:20 ` Daniel Baluta
2019-08-05 19:20 ` Daniel Baluta
2019-08-05 19:20 ` Daniel Baluta
2019-08-05 4:52 ` [RESEND PATCH v5 4/4] mailbox: imx: add support for imx v1 mu Richard Zhu
2019-08-05 4:52 ` Richard Zhu
2019-08-05 19:21 ` Daniel Baluta
2019-08-05 19:21 ` Daniel Baluta
2019-10-08 7:25 ` Daniel Baluta
2019-10-08 7:25 ` Daniel Baluta
2019-10-09 1:47 ` [EXT] " Richard Zhu
2019-10-09 1:47 ` Richard Zhu
2019-10-12 1:12 ` Richard Zhu
2019-10-12 1:12 ` Richard Zhu
2019-10-12 7:24 ` Daniel Baluta
2019-10-12 7:24 ` Daniel Baluta
[not found] ` <CAEnQRZDk4TjU0nWgGXEV06ZygvSyuPHc61_uT7KRu0j2Aaxj7w@mail.gmail.com>
2019-10-29 21:02 ` Jassi Brar [this message]
2019-10-29 21:02 ` Jassi Brar
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=CABb+yY1-PrmT_Qp6M1+WTnVAKizVqJLYJcip4KfqcAjcuN3GCg@mail.gmail.com \
--to=jassisinghbrar@gmail.com \
--cc=aisheng.dong@nxp.com \
--cc=daniel.baluta@gmail.com \
--cc=daniel.baluta@nxp.com \
--cc=hongxing.zhu@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=o.rempel@pengutronix.de \
--cc=shawnguo@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.