All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nishanth Menon <nm@ti.com>
To: Jan Kiszka <jan.kiszka@siemens.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
	Santosh Shilimkar <ssantosh@kernel.org>,
	Grzegorz Jaszczyk <grzegorz.jaszczyk@linaro.org>
Cc: Nishanth Menon <nm@ti.com>
Subject: Re: [PATCH] soc: ti: pruss: fix referenced node in error message
Date: Mon, 22 Nov 2021 20:04:10 -0600	[thread overview]
Message-ID: <163763303249.31252.7911231463957684515.b4-ty@ti.com> (raw)
In-Reply-To: <d6e24953-ea89-fd1c-6e16-7a0142118054@siemens.com>

Hi Jan Kiszka,

On Mon, 21 Jun 2021 20:08:28 +0200, Jan Kiszka wrote:
> From: Jan Kiszka <jan.kiszka@siemens.com>
> 
> So far, "(null)" is reported for the node that is missing clocks.
> 
> 

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

[1/1] soc: ti: pruss: fix referenced node in error message
      commit: 8aa35e0bb5eaa42bac415ad0847985daa7b4890c

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: Jan Kiszka <jan.kiszka@siemens.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
	Santosh Shilimkar <ssantosh@kernel.org>,
	Grzegorz Jaszczyk <grzegorz.jaszczyk@linaro.org>
Cc: Nishanth Menon <nm@ti.com>
Subject: Re: [PATCH] soc: ti: pruss: fix referenced node in error message
Date: Mon, 22 Nov 2021 20:04:10 -0600	[thread overview]
Message-ID: <163763303249.31252.7911231463957684515.b4-ty@ti.com> (raw)
In-Reply-To: <d6e24953-ea89-fd1c-6e16-7a0142118054@siemens.com>

Hi Jan Kiszka,

On Mon, 21 Jun 2021 20:08:28 +0200, Jan Kiszka wrote:
> From: Jan Kiszka <jan.kiszka@siemens.com>
> 
> So far, "(null)" is reported for the node that is missing clocks.
> 
> 

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

[1/1] soc: ti: pruss: fix referenced node in error message
      commit: 8aa35e0bb5eaa42bac415ad0847985daa7b4890c

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:[~2021-11-23  2:04 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-21 18:08 [PATCH] soc: ti: pruss: fix referenced node in error message Jan Kiszka
2021-06-21 18:08 ` Jan Kiszka
2021-06-23 15:51 ` Suman Anna
2021-06-23 15:51   ` Suman Anna
2021-09-01 15:03   ` Jan Kiszka
2021-09-01 15:03     ` Jan Kiszka
2021-11-20  7:53     ` Jan Kiszka
2021-11-20  7:53       ` Jan Kiszka
2021-11-22 15:30       ` Suman Anna
2021-11-22 15:30         ` Suman Anna
2021-11-23  2:04 ` Nishanth Menon [this message]
2021-11-23  2:04   ` 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=163763303249.31252.7911231463957684515.b4-ty@ti.com \
    --to=nm@ti.com \
    --cc=grzegorz.jaszczyk@linaro.org \
    --cc=jan.kiszka@siemens.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.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.