From: Nishanth Menon <nm@ti.com>
To: Mathieu Poirier <mathieu.poirier@linaro.org>
Cc: MD Danish Anwar <danishanwar@ti.com>,
Bjorn Andersson <andersson@kernel.org>, <rogerq@kernel.org>,
<vigneshr@ti.org>, <srk@ti.com>, <linux-kernel@vger.kernel.org>,
<linux-remoteproc@vger.kernel.org>, <linux-omap@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] remoteproc: pru: add support for configuring GPMUX based on client setup
Date: Mon, 5 Jun 2023 15:45:52 -0500 [thread overview]
Message-ID: <20230605204552.x4ctuzos4rysldwj@sessions> (raw)
In-Reply-To: <ZH4aywQoA9gy2OWU@p14s>
On 11:26-20230605, Mathieu Poirier wrote:
[...]
> Here I have to suppose pruss_cfg_get_gpmux() has been added to Nishanth's tree.
> As such the only way for me to apply your patch is if Nishanth sends me a pull
> request for the patchset that introduced pruss_cfg_get_gpmux(). You can also
> resend this in the next cycle.
Yes, I had pulled this in [1] along with a few other driver fixes. I
can send you an immutable tag to pull for your tree, if that helps the
process along though, it might have a unrelated driver fixup patch as
part of the series though..
[1] https://lore.kernel.org/all/168434617580.1538524.11482827517408254591.b4-ty@ti.com/
[2] https://git.kernel.org/pub/scm/linux/kernel/git/ti/linux.git/log/?h=ti-drivers-soc-next
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
WARNING: multiple messages have this Message-ID (diff)
From: Nishanth Menon <nm@ti.com>
To: Mathieu Poirier <mathieu.poirier@linaro.org>
Cc: MD Danish Anwar <danishanwar@ti.com>,
Bjorn Andersson <andersson@kernel.org>, <rogerq@kernel.org>,
<vigneshr@ti.org>, <srk@ti.com>, <linux-kernel@vger.kernel.org>,
<linux-remoteproc@vger.kernel.org>, <linux-omap@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] remoteproc: pru: add support for configuring GPMUX based on client setup
Date: Mon, 5 Jun 2023 15:45:52 -0500 [thread overview]
Message-ID: <20230605204552.x4ctuzos4rysldwj@sessions> (raw)
In-Reply-To: <ZH4aywQoA9gy2OWU@p14s>
On 11:26-20230605, Mathieu Poirier wrote:
[...]
> Here I have to suppose pruss_cfg_get_gpmux() has been added to Nishanth's tree.
> As such the only way for me to apply your patch is if Nishanth sends me a pull
> request for the patchset that introduced pruss_cfg_get_gpmux(). You can also
> resend this in the next cycle.
Yes, I had pulled this in [1] along with a few other driver fixes. I
can send you an immutable tag to pull for your tree, if that helps the
process along though, it might have a unrelated driver fixup patch as
part of the series though..
[1] https://lore.kernel.org/all/168434617580.1538524.11482827517408254591.b4-ty@ti.com/
[2] https://git.kernel.org/pub/scm/linux/kernel/git/ti/linux.git/log/?h=ti-drivers-soc-next
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
_______________________________________________
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:[~2023-06-05 20:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-01 10:59 [PATCH] remoteproc: pru: add support for configuring GPMUX based on client setup MD Danish Anwar
2023-06-01 10:59 ` MD Danish Anwar
2023-06-05 17:26 ` Mathieu Poirier
2023-06-05 17:26 ` Mathieu Poirier
2023-06-05 20:45 ` Nishanth Menon [this message]
2023-06-05 20:45 ` Nishanth Menon
2023-06-07 14:35 ` Mathieu Poirier
2023-06-07 14:35 ` Mathieu Poirier
2023-06-06 9:40 ` [EXTERNAL] " Md Danish Anwar
2023-06-06 9:40 ` Md Danish Anwar
-- strict thread matches above, loose matches on Subject: below --
2023-08-02 6:49 MD Danish Anwar
2023-08-21 21:21 ` Mathieu Poirier
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=20230605204552.x4ctuzos4rysldwj@sessions \
--to=nm@ti.com \
--cc=andersson@kernel.org \
--cc=danishanwar@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=rogerq@kernel.org \
--cc=srk@ti.com \
--cc=vigneshr@ti.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.