[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <169095298990.2814913.9232609485475584241.b4-ty@ti.com>
Date: Wed, 2 Aug 2023 00:10:07 -0500
From: Nishanth Menon <nm@...com>
To: Vignesh Raghavendra <vigneshr@...com>,
Santosh Shilimkar <ssantosh@...nel.org>,
Russell King <linux@...linux.org.uk>,
<linux-arm-kernel@...ts.infradead.org>,
<linux-kernel@...r.kernel.org>, Andrew Davis <afd@...com>
CC: Nishanth Menon <nm@...com>
Subject: Re: [PATCH v2 1/2] ARM: keystone: Merge memory.h into the only file that uses it
Hi Andrew Davis,
On Wed, 26 Jul 2023 11:04:40 -0500, Andrew Davis wrote:
> The defines in memory.h can go into the file that makes use of them.
> No reason to have a header here, remove.
>
>
I have applied the following to branch ti-keystone-next on [1].
Thank you!
[1/2] ARM: keystone: Merge memory.h into the only file that uses it
commit: 04a0137fc36d0b544afd5afd59f8f739ca97e33e
[2/2] ARM: keystone: Merge PM function into main support file
commit: d33dbddf43a055f69bda7f3488bb1e136d1b6bbc
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] https://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
Powered by blists - more mailing lists