From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 7751CC32789 for ; Tue, 23 Aug 2022 18:27:30 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231741AbiHWS12 (ORCPT ); Tue, 23 Aug 2022 14:27:28 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:54028 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231446AbiHWS1J (ORCPT ); Tue, 23 Aug 2022 14:27:09 -0400 Received: from dfw.source.kernel.org (dfw.source.kernel.org [IPv6:2604:1380:4641:c500::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 882B94CA13 for ; Tue, 23 Aug 2022 09:47:14 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id BFFA3616EC for ; Tue, 23 Aug 2022 16:47:13 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id BE086C43470; Tue, 23 Aug 2022 16:47:11 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1661273233; bh=RIh85e4avEVrE67f7p7cpqft653q9Drb4EcgsFrnCKw=; h=From:To:Cc:In-Reply-To:References:Subject:Date:From; b=TyTL6TuxDzfJTwlzoBVdx1ND/a+jcTAvLz79f/1sbW9v4k4BsNT5VApe1zQua9lPB tmkDcEWXTjQ58liHeUf7VMoK4rqd+lUCcGN9kA750Gak6lvDGfZgP//TxmjOncRy4/ 2OfXSCc23Nx/o7pLd1Mu5qokBF+467aFsis/56Ki+js1HGZvAohJhc/PcaNdWPICZQ c50K08dAsryvbm0r54JuOxMRWDYphBtXpTjT6oHwVS0eKHpdvMK47nTrv3q/0cRWx3 bJkYpSpmjXuGdT5SgGpHdZWC1MDLj1uPgCEbpOopMACRB0tmne1Y4VjMNSO2K0pil/ x0QPRq2WBZndQ== From: Mark Brown To: Dmitry Rokosov , andy.shevchenko@gmail.com, rafael@kernel.org, jic23@kernel.org, gregkh@linuxfoundation.org Cc: kernel , 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 X-Mailer: b4 0.10.0-dev-0c1df Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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