From: Vinod Koul <vkoul@kernel.org>
To: frank.li@nxp.com, Frank Li <Frank.Li@nxp.com>
Cc: dmaengine@vger.kernel.org, gregkh@linuxfoundation.org,
imx@lists.linux.dev, linux-kernel@vger.kernel.org, lkp@intel.com,
oe-kbuild-all@lists.linux.dev, rafael@kernel.org
Subject: Re: [PATCH v4 0/3] dmaengine: fsl_edma: add trace and debugfs support
Date: Thu, 28 Sep 2023 17:26:19 +0530 [thread overview]
Message-ID: <169590217975.152265.11376979671569668186.b4-ty@kernel.org> (raw)
In-Reply-To: <20230921150144.3260231-1-Frank.Li@nxp.com>
On Thu, 21 Sep 2023 11:01:41 -0400, Frank Li wrote:
> Change from v3 to v4
> - Fix build warning
>
> If you fix the issue in a separate patch/commit (i.e. not just a new version of
> the same patch/commit), kindly add following tags
> | Reported-by: kernel test robot <lkp@intel.com>
> | Closes: https://lore.kernel.org/oe-kbuild-all/202309210500.owiirl4c-lkp@intel.com/
>
> [...]
Applied, thanks!
[1/3] debugfs_create_regset32() support 8/16/64 bit width registers
commit: 09289d0ad1226c4735f8d9f68c9c3e54cbaba3d4
[2/3] dmaengine: fsl-emda: add debugfs support
commit: 105c148c66fa06ca2a375edacfa3139c814af9d1
[3/3] dmaengine: fsl-edma: add trace event support
commit: c8fde7598064fc9b94a53264b1e0c605a140fedb
Best regards,
--
~Vinod
prev parent reply other threads:[~2023-09-28 11:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-21 15:01 Frank Li
2023-09-21 15:01 ` [PATCH v4 1/3] debugfs_create_regset32() support 8/16/64 bit width registers Frank Li
2023-09-21 15:01 ` [PATCH v4 2/3] dmaengine: fsl-emda: add debugfs support Frank Li
2023-09-21 15:01 ` [PATCH v4 3/3] dmaengine: fsl-edma: add trace event support Frank Li
2023-09-28 11:56 ` Vinod Koul [this message]
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=169590217975.152265.11376979671569668186.b4-ty@kernel.org \
--to=vkoul@kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=frank.li@nxp.com \
--cc=gregkh@linuxfoundation.org \
--cc=imx@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--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®