Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
From:   Mark Brown <broonie@kernel.org>
To:     Dmitry Rokosov <DDRokosov@sberdevices.ru>,
        andy.shevchenko@gmail.com, rafael@kernel.org, jic23@kernel.org,
        gregkh@linuxfoundation.org
Cc:     kernel <kernel@sberdevices.ru>, linux-kernel@vger.kernel.org
In-Reply-To: <20220816181451.5628-1-ddrokosov@sberdevices.ru>
References: <20220816181451.5628-1-ddrokosov@sberdevices.ru>
Subject: Re: [PATCH v1] regmap: introduce value tracing for regmap bulk operations
Message-Id: <166127323148.445898.2568312423434118605.b4-ty@kernel.org>
Date:   Tue, 23 Aug 2022 17:47:11 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Precedence: bulk

On Tue, 16 Aug 2022 18:14:48 +0000, Dmitry Rokosov wrote:
> Currently, only one-register io operations support tracepoints with
> value logging. For the regmap bulk operations developer can view
> hw_start/hw_done tracepoints with starting reg number and registers
> count to be reading or writing. This patch injects tracepoints with
> dumping registers values in the hex format to regmap bulk reading
> and writing.
> 
> [...]

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regmap.git for-next

Thanks!

[1/1] regmap: introduce value tracing for regmap bulk operations
      commit: 026c99b508f060d3c85fda06b21e010683ef5590

All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a 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.

Thanks,
Mark