Linux RDMA and InfiniBand development
 help / color / mirror / Atom feed
From: Leon Romanovsky <leon@kernel.org>
To: jgg@ziepe.ca, Junxian Huang <huangjunxian6@hisilicon.com>
Cc: linux-rdma@vger.kernel.org, linuxarm@huawei.com,
	tangchengchang@huawei.com
Subject: Re: [PATCH for-next 0/6] RDMA/hns: Add trace support
Date: Mon, 21 Apr 2025 15:20:13 +0300	[thread overview]
Message-ID: <20250421122013.GB10551@unreal> (raw)
In-Reply-To: <174515167383.720316.10548192191975881376.b4-ty@kernel.org>

On Sun, Apr 20, 2025 at 08:21:13AM -0400, Leon Romanovsky wrote:
> 
> On Fri, 18 Apr 2025 16:56:41 +0800, Junxian Huang wrote:
> > Add trace support for hns. Set tracepoints for flushe CQE, WQE,
> > AEQE, MT/MTR and CMDQ.
> > 
> > Patch #5 fixes the dependency issue of hns_roce_hw_v2.h on hnae3.h,
> > otherwise there will be a compilation error when hns_roce_hw_v2.h
> > is included in hns_roce_trace.h in patch #6.
> > 
> > [...]
> 
> Applied, thanks!

I dropped this.

Thanks

  reply	other threads:[~2025-04-21 12:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-18  8:56 [PATCH for-next 0/6] RDMA/hns: Add trace support Junxian Huang
2025-04-18  8:56 ` [PATCH for-next 1/6] RDMA/hns: Add trace for flush CQE Junxian Huang
2025-04-18  8:56 ` [PATCH for-next 2/6] RDMA/hns: Add trace for WQE dumping Junxian Huang
2025-04-18  8:56 ` [PATCH for-next 3/6] RDMA/hns: Add trace for AEQE dumping Junxian Huang
2025-04-18  8:56 ` [PATCH for-next 4/6] RDMA/hns: Add trace for MR/MTR attribute dumping Junxian Huang
2025-04-18  8:56 ` [PATCH for-next 5/6] RDMA/hns: Include hnae3.h in hns_roce_hw_v2.h Junxian Huang
2025-04-18  8:56 ` [PATCH for-next 6/6] RDMA/hns: Add trace for CMDQ dumping Junxian Huang
2025-04-20 12:21 ` [PATCH for-next 0/6] RDMA/hns: Add trace support Leon Romanovsky
2025-04-21 12:20   ` Leon Romanovsky [this message]
2025-04-20 15:11 ` Leon Romanovsky
2025-04-21 13:01   ` Junxian Huang

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=20250421122013.GB10551@unreal \
    --to=leon@kernel.org \
    --cc=huangjunxian6@hisilicon.com \
    --cc=jgg@ziepe.ca \
    --cc=linux-rdma@vger.kernel.org \
    --cc=linuxarm@huawei.com \
    --cc=tangchengchang@huawei.com \
    /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