All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nishanth Menon <nm@ti.com>
To: <kishon@ti.com>, Santosh Shilimkar <ssantosh@kernel.org>,
	<robh+dt@kernel.org>, <krzysztof.kozlowski+dt@linaro.org>
Cc: Nishanth Menon <nm@ti.com>, <devicetree@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v2 0/3] soc: ti: Enable PRUSS-M on K3 AM62x SoCs
Date: Wed, 6 Jul 2022 20:32:20 -0500	[thread overview]
Message-ID: <165715751131.13899.13575622163713298040.b4-ty@ti.com> (raw)
In-Reply-To: <20220602120613.2175-1-kishon@ti.com>

Hi Kishon Vijay Abraham I,

On Thu, 2 Jun 2022 17:36:10 +0530, Kishon Vijay Abraham I wrote:
> Series adds AM62x specific compatible string to enable PRUSS-M in
> AM62x SoCs.
> 
> Changes from v1:
> 1) Added a new patch to re-arrange "compatible" in alphabetic
>    order
> 
> [...]

I have applied the following to branch ti-drivers-soc-next on [1].
Thank you!

[1/3] dt-bindings: soc: ti: pruss: Re-arrange "compatible" in alphabetic order
      commit: b8c8d647f2fe4e263864b800f4647431ec0aabdf
[2/3] dt-bindings: soc: ti: pruss: Update bindings for K3 AM62x SoCs
      commit: 75938bab63a4bf5c654360aebfb96235de10d882
[3/3] soc: ti: pruss: Enable support for PRUSS-M subsystem on K3 AM62x SoCs
      commit: f16afe238a7ff3c71a943cf74392538974c29b22

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/ti/linux.git
-- 
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: <kishon@ti.com>, Santosh Shilimkar <ssantosh@kernel.org>,
	<robh+dt@kernel.org>, <krzysztof.kozlowski+dt@linaro.org>
Cc: Nishanth Menon <nm@ti.com>, <devicetree@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v2 0/3] soc: ti: Enable PRUSS-M on K3 AM62x SoCs
Date: Wed, 6 Jul 2022 20:32:20 -0500	[thread overview]
Message-ID: <165715751131.13899.13575622163713298040.b4-ty@ti.com> (raw)
In-Reply-To: <20220602120613.2175-1-kishon@ti.com>

Hi Kishon Vijay Abraham I,

On Thu, 2 Jun 2022 17:36:10 +0530, Kishon Vijay Abraham I wrote:
> Series adds AM62x specific compatible string to enable PRUSS-M in
> AM62x SoCs.
> 
> Changes from v1:
> 1) Added a new patch to re-arrange "compatible" in alphabetic
>    order
> 
> [...]

I have applied the following to branch ti-drivers-soc-next on [1].
Thank you!

[1/3] dt-bindings: soc: ti: pruss: Re-arrange "compatible" in alphabetic order
      commit: b8c8d647f2fe4e263864b800f4647431ec0aabdf
[2/3] dt-bindings: soc: ti: pruss: Update bindings for K3 AM62x SoCs
      commit: 75938bab63a4bf5c654360aebfb96235de10d882
[3/3] soc: ti: pruss: Enable support for PRUSS-M subsystem on K3 AM62x SoCs
      commit: f16afe238a7ff3c71a943cf74392538974c29b22

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/ti/linux.git
-- 
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

  parent reply	other threads:[~2022-07-07  1:32 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-02 12:06 [PATCH v2 0/3] soc: ti: Enable PRUSS-M on K3 AM62x SoCs Kishon Vijay Abraham I
2022-06-02 12:06 ` Kishon Vijay Abraham I
2022-06-02 12:06 ` [PATCH v2 1/3] dt-bindings: soc: ti: pruss: Re-arrange "compatible" in alphabetic order Kishon Vijay Abraham I
2022-06-02 12:06   ` Kishon Vijay Abraham I
2022-06-02 12:20   ` Krzysztof Kozlowski
2022-06-02 12:20     ` Krzysztof Kozlowski
2022-06-02 12:06 ` [PATCH v2 2/3] dt-bindings: soc: ti: pruss: Update bindings for K3 AM62x SoCs Kishon Vijay Abraham I
2022-06-02 12:06   ` Kishon Vijay Abraham I
2022-06-02 12:20   ` Krzysztof Kozlowski
2022-06-02 12:20     ` Krzysztof Kozlowski
2022-06-02 12:06 ` [PATCH v2 3/3] soc: ti: pruss: Enable support for PRUSS-M subsystem on " Kishon Vijay Abraham I
2022-06-02 12:06   ` Kishon Vijay Abraham I
2022-07-07  1:32 ` Nishanth Menon [this message]
2022-07-07  1:32   ` [PATCH v2 0/3] soc: ti: Enable PRUSS-M " Nishanth Menon

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=165715751131.13899.13575622163713298040.b4-ty@ti.com \
    --to=nm@ti.com \
    --cc=devicetree@vger.kernel.org \
    --cc=kishon@ti.com \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=ssantosh@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.