All of lore.kernel.org
 help / color / mirror / Atom feed
From: Braden Zhang <braden_zhang@lecomputing.com>
To: helgaas@kernel.org, Bjorn Helgaas <bhelgaas@google.com>
Cc: braden_zhang@lecomputing.com, brett_zhou@lecomputing.com,
	jingoohan1@gmail.com, linux-kernel@vger.kernel.org,
	linux-pci@vger.kernel.org, mani@kernel.org
Subject: Re: [v3,v3] PCI: dwc: Add pci id for LECARC pcie pmu
Date: Tue, 21 Jul 2026 10:04:06 +0800	[thread overview]
Message-ID: <20260721020406.1701864-1-braden_zhang@lecomputing.com> (raw)
In-Reply-To: <20260713173805.GA1223423@bhelgaas>

> I gave you some comments but did not provide a "Reviewed-by" tag, so
> including one here is not valid, see:

Bjorn, thanks for the review !

Sorry for mis-used the  "Reviewed-by" tag.
I'm still getting familiar with the b4 tool and the patch submission workflow.
I'll go through the documentation you referenced to make sure I get the process right going forward.

For the next version (v4), I will:

Drop the invalid Reviewed-by tag.

Reword the commit message as you suggested and wrap it to 75 columns.

Fix the capitalization in the subject line (s/pci/PCI/, etc.).

Will send out v4 shortly.

Thanks,
Braden Zhang

  reply	other threads:[~2026-07-21  2:37 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-13  2:10 [PATCH v3 v3] PCI: dwc: Add pci id for LECARC pcie pmu Braden Zhang
2026-07-13  2:31 ` sashiko-bot
2026-07-13  5:14 ` Manivannan Sadhasivam
2026-07-20  7:43   ` Braden Zhang
2026-07-20 12:31     ` Manivannan Sadhasivam
2026-07-13 17:38 ` Bjorn Helgaas
2026-07-21  2:04   ` Braden Zhang [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-07-21  6:21 [PATCH v4 v4] PCI: dwc: Add PCI ID for LECARC PCIe pmu Braden Zhang
2026-07-21  6:36 ` Manivannan Sadhasivam
2026-07-21  8:04   ` Braden Zhang
2026-07-21  8:09   ` Braden Zhang
2026-07-21  6:49 ` sashiko-bot

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=20260721020406.1701864-1-braden_zhang@lecomputing.com \
    --to=braden_zhang@lecomputing.com \
    --cc=bhelgaas@google.com \
    --cc=brett_zhou@lecomputing.com \
    --cc=helgaas@kernel.org \
    --cc=jingoohan1@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=mani@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.