mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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
Subject: Re: [PATCH v1] regmap: introduce value tracing for regmap bulk operations
Date: Tue, 23 Aug 2022 17:47:11 +0100	[thread overview]
Message-ID: <166127323148.445898.2568312423434118605.b4-ty@kernel.org> (raw)
In-Reply-To: <20220816181451.5628-1-ddrokosov@sberdevices.ru>

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

  parent reply	other threads:[~2022-08-23 18:27 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-16 18:14 Dmitry Rokosov
2022-08-18 12:15 ` Dmitry Rokosov
2022-08-18 13:49   ` Marc Zyngier
2022-08-18 15:43     ` Mark Brown
2022-08-18 17:44       ` Dmitry Rokosov
2022-08-19 12:07         ` Mark Brown
2022-08-19 13:31           ` Dmitry Rokosov
2022-08-19 14:44             ` Mark Brown
2022-08-19 15:22               ` Dmitry Rokosov
2022-08-19 14:25       ` Marc Zyngier
2022-08-19 14:38         ` Mark Brown
2022-08-19 15:31           ` Dmitry Rokosov
2022-08-18 17:02     ` Dmitry Rokosov
2022-08-23 16:47 ` Mark Brown [this message]
2022-08-23 21:39 ` Andy Shevchenko
2022-08-31  0:45   ` Dmitry Rokosov
2022-09-01 13:16     ` Andy Shevchenko

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=166127323148.445898.2568312423434118605.b4-ty@kernel.org \
    --to=broonie@kernel.org \
    --cc=DDRokosov@sberdevices.ru \
    --cc=andy.shevchenko@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jic23@kernel.org \
    --cc=kernel@sberdevices.ru \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rafael@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®