From: Nishanth Menon <nm@ti.com>
To: Tero Kristo <t-kristo@ti.com>,
Santosh Shilimkar <ssantosh@kernel.org>,
Peter Ujfalusi <peter.ujfalusi@ti.com>,
<santosh.shilimkar@oracle.com>,
Grygorii Strashko <grygorii.strashko@ti.com>
Cc: Nishanth Menon <nm@ti.com>, <linux-kernel@vger.kernel.org>,
Vignesh Raghavendra <vigneshr@ti.com>,
Sekhar Nori <nsekhar@ti.com>,
<linux-arm-kernel@lists.infradead.org>,
Rob Herring <robh+dt@kernel.org>
Subject: Re: [PATCH next v2 0/3] soc: ti: k3: ringacc: add am65x sr2.0 support
Date: Mon, 14 Sep 2020 07:34:39 -0500 [thread overview]
Message-ID: <160008683286.21302.10845118207565494240.b4-ty@ti.com> (raw)
In-Reply-To: <20200829184139.15547-1-grygorii.strashko@ti.com>
On Sat, 29 Aug 2020 21:41:36 +0300, Grygorii Strashko wrote:
> I've rebased on top of linux-next and identified merge conflict of patch 3
> with commit 6da45875fa17 ("arm64: dts: k3-am65: Update the RM resource types")
> in -next.
Hi Grygorii Strashko,
I have applied the following to branch ti-k3-dts-next on [1].
Thank you!
[1/1] arm64: dts: ti: k3-am65: ringacc: drop ti, dma-ring-reset-quirk
commit: 69fba6172b9f03ad1079c9c72f5cf0c623a18c6d
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent up the chain during
the next merge window (or sooner if it is a relevant bug fix), however if
problems are discovered then the patch may be dropped or reverted.
You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.
If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.
Please add any relevant lists and maintainers to the CCs when replying
to this mail.
[1] git://git.kernel.org/pub/scm/linux/kernel/git/nmenon/linux.git
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
prev parent reply other threads:[~2020-09-14 12:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-29 18:41 [PATCH next v2 0/3] soc: ti: k3: ringacc: add am65x sr2.0 support Grygorii Strashko
2020-08-29 18:41 ` [PATCH next v2 1/3] " Grygorii Strashko
2020-08-29 18:41 ` [PATCH next v2 2/3] bindings: soc: ti: soc: ringacc: remove ti,dma-ring-reset-quirk Grygorii Strashko
2020-08-29 18:41 ` [PATCH next v2 3/3] arm64: dts: ti: k3-am65: ringacc: drop ti,dma-ring-reset-quirk Grygorii Strashko
2020-08-31 18:34 ` [PATCH next v2 0/3] soc: ti: k3: ringacc: add am65x sr2.0 support santosh.shilimkar
2020-09-02 14:08 ` Nishanth Menon
2020-09-09 16:52 ` santosh.shilimkar
2020-09-12 4:54 ` santosh.shilimkar
2020-09-08 22:09 ` Suman Anna
2020-09-09 2:40 ` santosh.shilimkar
2020-09-12 4:55 ` santosh.shilimkar
2020-09-14 12:34 ` 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=160008683286.21302.10845118207565494240.b4-ty@ti.com \
--to=nm@ti.com \
--cc=grygorii.strashko@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nsekhar@ti.com \
--cc=peter.ujfalusi@ti.com \
--cc=robh+dt@kernel.org \
--cc=santosh.shilimkar@oracle.com \
--cc=ssantosh@kernel.org \
--cc=t-kristo@ti.com \
--cc=vigneshr@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).