From: Simon Horman <horms@kernel.org>
To: Nishanth Menon <nm@ti.com>
Cc: Santosh Shilimkar <ssantosh@kernel.org>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] soc: ti: pruss: Allow compile-testing
Date: Fri, 19 May 2023 18:51:04 +0200 [thread overview]
Message-ID: <ZGeo+Nauwemwtc5v@kernel.org> (raw)
In-Reply-To: <168434612546.1538453.14483208071718769411.b4-ty@ti.com>
On Wed, May 17, 2023 at 12:56:08PM -0500, Nishanth Menon wrote:
> Hi Simon Horman,
>
> On Thu, 11 May 2023 16:54:36 +0200, Simon Horman wrote:
> > Allow compile testing of TI PRU-ICSS Subsystem Platform drivers.
> > This allows for improved build-test coverage.
> >
> > No functional change intended.
> >
> >
>
> I have applied the following to branch ti-drivers-soc-next on [1].
> NOTE: I did'nt see any immediate issue with this patch, but hopefully we dont
> break COMPILE_TEST going ahead. Lets see.
> Thank you!
Thanks. I'll look out for any notices regarding breakage.
> [1/1] soc: ti: pruss: Allow compile-testing
> commit: e752f9b924a1fd1afcf36e51b03dfa9c3096a3bd
>
> 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
WARNING: multiple messages have this Message-ID (diff)
From: Simon Horman <horms@kernel.org>
To: Nishanth Menon <nm@ti.com>
Cc: Santosh Shilimkar <ssantosh@kernel.org>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] soc: ti: pruss: Allow compile-testing
Date: Fri, 19 May 2023 18:51:04 +0200 [thread overview]
Message-ID: <ZGeo+Nauwemwtc5v@kernel.org> (raw)
In-Reply-To: <168434612546.1538453.14483208071718769411.b4-ty@ti.com>
On Wed, May 17, 2023 at 12:56:08PM -0500, Nishanth Menon wrote:
> Hi Simon Horman,
>
> On Thu, 11 May 2023 16:54:36 +0200, Simon Horman wrote:
> > Allow compile testing of TI PRU-ICSS Subsystem Platform drivers.
> > This allows for improved build-test coverage.
> >
> > No functional change intended.
> >
> >
>
> I have applied the following to branch ti-drivers-soc-next on [1].
> NOTE: I did'nt see any immediate issue with this patch, but hopefully we dont
> break COMPILE_TEST going ahead. Lets see.
> Thank you!
Thanks. I'll look out for any notices regarding breakage.
> [1/1] soc: ti: pruss: Allow compile-testing
> commit: e752f9b924a1fd1afcf36e51b03dfa9c3096a3bd
>
> 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
>
next prev parent reply other threads:[~2023-05-19 16:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-11 14:54 [PATCH] soc: ti: pruss: Allow compile-testing Simon Horman
2023-05-17 17:56 ` Nishanth Menon
2023-05-17 17:56 ` Nishanth Menon
2023-05-19 16:51 ` Simon Horman [this message]
2023-05-19 16:51 ` Simon Horman
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=ZGeo+Nauwemwtc5v@kernel.org \
--to=horms@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nm@ti.com \
--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.